Maria Delia

After reading Apprenticeship Patterns, I see being a software engineer in a different lens. I did get into Computer Science initially because I was really good in science and the salaries were looking great, but I think it is really important for people that are looking to go into the tech industry and create new software, to really understand who you need to become. I believe the book really explains the hardships, importance of focus, humility, being intentional with your learning as you go into the career.

Before this reading, I viewed growth mostly in terms of learning new technologies or building impressive projects. However, the authors explain apprenticeship as a mindset. The difference between apprentice, journeyman, and master is not about job titles, but about responsibility and focus. The explanation on this progression made me realize that technical ability alone is not the goal but growing in responsibility and having an impact in the community matters just as much.

The introduction of Chapter 2, Emptying the Cup, I particularly liked. The Zen story about the overflowing teacup illustrates how ego and prior knowledge can block real learning. The reason why I liked it is because it gave me a completely different point of view when it comes to how people perceive themselves in the field when it comes to the skills you build  in the journey. I always saw myself as never knowing enough, being overly humble because of how much there is to know. It was interesting to see that there are also those who have learned multiple languages and frameworks might have it easy to assume competence transfers automatically. But the idea of “wearing the white belt” suggests that real progress requires humility. I guess the imposter syndrome in me serves for something good too.

Chapter 3’s theme of Walking the Long Road also felt deeply relevant. The authors put a great importance on sustainable motivation and choosing growth over shortcuts. In a field where quick success and high salaries are often highlighted and attracted so many in this field, this chapter reframes success as long-term mastery rather than rapid advancement. It made me question whether I sometimes prioritize outcomes (grades, internships, resume lines) over the depth of understanding.

The introductions to Chapters 4–6 suggest that accurate self-assessment, perpetual learning, and constructing your own curriculum are essential habits. That idea is both motivating and intimidating. I think that the CS major itself should be teaching the ‘behind the scenes’ part for us to understand the reasoning behind why things are done and the effect they have. It is our responsibility to learn the coding languages on our own. I understand that it could be harder for some people to self-study, but on the other hand you get to pick what you want to be a master in.

Overall, this reading made me reflect on the fact that becoming a great developer is less about reaching a destination and more about committing to the process of mastery.