Hello, today I was finishing reading Apprenticeship Patterns and I want to use this blog to reflect upon the concepts that caught my attention and I want to explore more into the future. In the book it describes how students and self taught developers use these ideas suggested in the text book to further improve themselves in their skills to the “master” that they want to be in the career. From my interpretation, a “master” is someone who knows a lot about coding languages and a set of skills that you can trust with the project. Even though the book suggests that being a master at programming is the end but to me personally that is not the end where people should stop at. It should be the point where you learn to improve on aspects you are passionate or wanting to learn. Let me explain further, computer science and programming tools change so much that it is challenging to evolve the old restrictions to new ones and how difficult it is to keep adapting that is why it is challenging even at that point.
That is why the book suggests people should have sustainable motivations and testing your coding skills. These are how you can prove to yourself that you are in the right field and find areas in your skills you need to improve to get to where you want to be. It is not an easy path. This path is a long one but it is very rewarding when you look back on how much you have improved and the challenges you have overcome.
Looking back at this book on page 45 it says “To only a fraction of the human race does God give the privilege of earning one’s bread doing what one would have gladly pursued free, for passion…” (Fredrick Brooks, The Mythical Man Month). Let me explain further, that it is very rare for people to find a job that people would learn themselves even if they were not paid. This passion is a good motivator but it can change due to influences in life like work and responsibilities but if maintained and changes to what you want it will cause you to push more into that enjoyment and journey. The journey of becoming the developer you want to be, challenges you tells you that you are improving.
According to the book which I agree with personally on page 85 it says “Self-examination is hard, but I believe we can learn more from studying our failures than our success” (Norm Kerth, Project Retrospectives). When you fail at something it shows you how you can improve upon it but not just that it can teach you more things about yourself. For example when to be humble and ask for help or being more responsible on managing time between hobby and work. These lessons can help you create a system for yourself so that you can constantly learn in the future even though failing can demotivate anyone.
Site Title 