Apprenticeship Patterns & Afterthoughts

Recently I started reading Apprenticeship Patterns by Adewale Oshineye & Dave Hoover. The main focus of this book focuses on the three stages of becoming a software Craftsman which includes the Apprentice, Journeyman and Master. While this may be the overall summary, there was much more to it. The first thing I noticed when it came to reading the introduction and the first couple of chapters was that this book was not just spitting a bunch of software information back at me while I try to retain it. It focused on preparing for and what I should expect, and be ready to do when it comes to joining the workforce. When speaking about the different topics, they go back to one man’s story and his relationship with apprenticeship patterns. His story focuses on how he had to go back to the basics and how to mentally prepare for that. While he had been a master in one language, he had to start back to the beginning when learning another. He had to make the conscious decision and decide to wear the ‘white belt’ again. What this meant was that he had to strip away all of what he had been taught and known about his previous language and start from scratch again. What first intrigued me was Dave’s story. It in some way relieved me to hear that Dave had to go back to wearing the white belt, even though he had been really skilled in another. I also feel that Daves story really goes in hand with what Chapter two was focused on. When I first started Computer Science I knew absolutely zero about it. I didn’t even know what my field had consisted of and what I would be doing with that major. Although I knew nothing, and where in classes with students (mostly men) who had a better understanding of what was going on, I am really happy that I had started that way. There was nothing that was going to affect my thoughts and ideas about the various languages I was learning. What I especially loved aout all of these chapters in general was that they gave various scenarios of work environments and what the problem & solution were and how to take action. Multiple of these scenarios have to do with an employee(yourself) who feels very out of place whether it be your excitement towards a new project, a new job, how to deal with not knowing as much as others in your group, and many more. Overall I believe that chapter two was the most relevant to me. Although this reading was very long it was extremely helpful and made me feel more at ease for the future. It also made me realize that although this field can make a lot of money, it is because it is a constantly changing field, and you always have to be updated on what is going on, that you are making this money. Languages are always changing, improving themselves and technology is always shooting for the future.

From the blog mrogers4836 by mrogers4836 and used with permission of the author. All other rights reserved by the author.

Apprenticeship Patterns

Apprenticeship Patterns: Guidance for the Aspiring Software Craftsman by Dave Hoover and Adewale Oshineye introduced me to the concept of an apprenticeship pattern. The first thing I thought of when I read the title of the book was the Gang of Four patterns that I became very familiar with in my previous semester. It is not surprising to me that many different work concepts and processes can be summarized by different patterns. Humans are pretty habitual, and we are good at finding out what works. With this in mind, I have a great amount of faith in the value and usefulness of these patterns.

The chapters following the introduction begin to introduce us to some of these patterns. The patterns that were introduced all have a lot in common. The most important thing seems to be the willingness and the drive to learn, independently of an instructor or master. Another important concept is the ability to get rid of preconceived notions and past knowledge that may not be as relevant or helpful as one might think. Wanting to learn and having to learn are two different processes and they will have different effects on your progress overall.

The short story about the master and the student at the beginning of Chapter 2 did a great job at illustrating an issue I run into a lot, being that it is hard to learn new things when you already know so much about something. Your previous knowledge definitely colors your perspective of new, similar things, and it can lead to a lot of dangerous assumptions. As scientists and engineers, we should never be making assumptions!

Another concept that showed up time and time again was not being afraid to fail. This idea is really close to me, as I have always believed that you learn a lot more from terrible failure than monumental success. There is so much value in learning how things can go wrong. That’s why chapter five definitely stood out for me. Anyone who thinks there is nothing more to learn will avoid all knowledge to prove themselves right. Every person you meet, whether you consider them above your level or below, has some new knowledge and information to offer from their experiences.

Overall, I think the book is a well-researched and accurate observation about the patterns of work and learning that fall behind “apprenticeships.” We can use these patterns to better understand how we work, as well as where our work can go wrong. Once we are able to acknowledge things about yourself such as your skill level, knowledge, and experience you can perform better and learn to learn so you can be the best version of you. You can’t improve until you know what improvement you are capable of.

From the blog CS@Worcester – Let's Get TechNICKal by technickal4 and used with permission of the author. All other rights reserved by the author.

Intro post

This is my intro post

From the blog CS@Worcester – The Average CS Student by Nathan Posterro and used with permission of the author. All other rights reserved by the author.

CS-448 MW 11:30-12:30 Introduction

Hello everybody,

I’m looking forward to having class with you all this semester! :]

Best,

Ryan

From the blog CS@Worcester – Bit by Bit by rdentremont58 and used with permission of the author. All other rights reserved by the author.

Post 0

Hello, world

From the blog cs-wsu – klapointe blog by klapointe2 and used with permission of the author. All other rights reserved by the author.

Software Capstone Introduction

This semester, I begin my software development Capstone, where I get to work with my peers on a semester long project. I will be making posts and reporting on my progress periodically throughout the semester on this blog, so keep up if you’re interested.

From the blog CS@Worcester – Let's Get TechNICKal by technickal4 and used with permission of the author. All other rights reserved by the author.

Introduction

Welcome! My name is Gulshan Kumar and I am creating this blog to help document the various subjects I will encounter while participating in my Computer Science Software Development Capstone. I hope you all learn as much as I do!

From the blog CS@Worcester – Student To Scholar by kumarcomputerscience and used with permission of the author. All other rights reserved by the author.

CS-448 Introduction

Hey everybody, my name is Dexter Canton. This blog is for CS-448, Im looking forward to sharing my posts with you all.

From the blog CS@Worcester – Dcanton Blog by dcantonblog and used with permission of the author. All other rights reserved by the author.

Software Dev Capstone

Hello all,

This is the last semester of my CS journey; Spring 2019. This post is for CS 448, the software dev capstone course.

Stay tuned,

Harry

From the blog CS@Worcester – Life in the Field of Computer Science by iharrynguyen and used with permission of the author. All other rights reserved by the author.

Back to Computer Science

Hello again, welcome to back to school. Most of us are senior which are wonderful. This going to be interesting semester. I am looking forward to work with you guys.

From the blog CS@Worcester – Nhat's Blog by Nhat Truong Le and used with permission of the author. All other rights reserved by the author.