
Hello, Deubg Ducker here, and I recently read the first few chapters of Apprenticeship Patterns by Dave Hoover and Adewale Oshineye. Let me say that I found it a very interesting read.
The basic gist of the book is that it takes the idea of being an apprentice as a Software developer and you being the software craftsman that will build their skills over years, and the books helps you understand how this process would go. its a guide for someones software development journey and introduces several good ideas for a developer like me.
An example of one of theses ideas is to focus on a The Second chapter’s “First Language”, which basically means hones your skill for one languages. Its more of a guide for those starting off but I feel in a way I follow this advice a lot. I tend to solve problems in languages that I am currently developing for, as of now Java, whether it be school or personal projects which help with honing my own skills for it. Also as I code more in the language I can see my skills improving which is what the book suggest. This part of the book speaks a lot to me as a developer and I think it will help many newcomers.
I say that is one of the most important chapters in the books but Chapter 4 feel is important for others on their journey. “Accurate Self-Assessment”, I think is a self-humbling exercise. It basically puts you the developer in a position of recognizing that you only know so much and can still build your skills. You can be competent in something but it may take a while for you to be an expert on it, saying that you are still on a long road. It reminds you that the journey doesn’t end when you fine the “I made it” phase, as you still have a lot to learn and I feel that this chapter reflects that.
This books is great and I wish I had this when I first started out, it would of probably helped me a lot on my journey. Thank you all for your time, and have a nice day.
From the blog Debug Duck by debugducker and used with permission of the author. All other rights reserved by the author.