In the third chapter of the Software Craftsman, the author goes in depth of what Software craftsman actually is. The author uses this term in order to describe good and angelic developers who always want to do their best and give their project the most value they can ever give it. They want to be productive and get things moving along and just leave things in a cluster, and that means with clients and publishers as well. I guess this is what he calls a ‘Dream Team’.
In my opinion, this probably should end up being the whole resolve of the book even though its just a chapters that’s not even the first one the author dives into. I feel like in this chapter the author is being kind of sarcastic because he does not tell you what the definition of being a Software Craftsman is. He is telling you what it isn’t and also what other sources say such as wikipedia. Instead of getting straight to the point he just mocks the reader. Later on he finally stats that Software Craftsmanship is about professionalism in software development. This chapter could have been straight to the point and overall shorter. I’m reading to learn not to waste time.
In the fourth chapter, the author continues touching base on developers’ behaviors except this time he is talking about the attitude toward the project. Making a good point that if we think good code from the past is still good, then we are not learning anything, the author goes into how much craftsman care about their work, which also includes discovering new things and adapt to better outcomes to help suit development in this future time-frame.
This chapter came to me as a good advice kind of area where he mentions good practices a developer should commit too on their own time that inflicts on their skills. Always practicing, staying up-to-date and keeping communication with the outside world are great ways to actually stay in shape as a developer and evolve the precious skill set.
Dan's Tech Rant 