Chapter One:

My first reaction to chapter one is that I am the intended audience for this book. I am somebody that wants to create software, but I need some guidance. I also noticed that Dave did not really start to program until he was 26. So many stories of great programmers start when the protoganist is 10. So it is encouraging to see somebody that started later in life. I also thought it was interesting that Dave had to “swallow his pride” in order to become proficient in his first programming language.

One Idea I found thought provoking is that software craftmanship is the “growth mindset”, which is more about sustained effort, as opposed to natural born talent. One thing that new developers struggle with is imposter syndrome. And I believe that this mindset could be an anectdote to imposter syndrome. This idea helped me to think about software development expertise as something that is gained through effort. Which is not always what we are told in pop culture.

Introductions for chapter 2-6:

Chapter two is called I emptying your cup. This is the idea that as an apprentice, I should be open to new ways of doing things. When I start my first job, I will not have a problem accepting advise. But this is a good concept to keep in mind as I progress. The long road is about the life long journey of improving as a developer. This is an inspiring idea. It makes me feel like it is not simply about how long you have been coding, as long as we continue to practice and learn. Chapter four is about accurate self assessment. This involves focusing on self improvement over being the best, or being better than average. This chapter sound interesting, because this is advice that I have heard in many aspects of life. So I am interested to see how the author relates this wisdom into software development.

Chapter five is called Perceptual Learning. I believe what the author is getting at is “learning how to learn”. This chapter stands out as being the most useful to me. No matter what stack I end up using at my first job, I will not know everything that I need for the job. So the ability to effectively learn on the job is crucial. Chapter six is about Building your own curriculum. In which the authors talk about the importance of books over internet resources. This may be the only thing I disagree with so far. In my experience so far, online resources like documentaion, tutorials, and stack overflow are more helpful than programming textbooks. But I could be wrong, I certainly don’t want to go into this book with a full cup.