In the first chapter of Software Craftsman, the author talks about how working in the industry was different in the past compared today. He makes remarks that even though people who work in the industry have been there for a long time and have gotten the Senior rank, it does not mean that they have the assumed knowledge that a Senior rank developer should have. Nowadays, companies are wanting professional work and professionally made projects, unlike back when they used to hire cheap coders who thought they knew what they were doing.
I kind of have to agree with the whole senior rank topic when it comes to knowledge. Not everyone is as fresh when they reach senior rank and they would usually depend on the internet and make excuses to go through their day. While it could be anyone, the seniors have an ideal image as they are looked up to as leader so its interesting how today plays out.
In the second chapter of Software Craftsman goes into the topic of being Agile, as did the Clean Coder in the previous book. Talking about the two groups, process-oriented and technical-oriented. Process-oriented focused on what is priority to finish while technical-oriented aims for teams to focus on quality. The author then talks about the Agile manifesto which comes with the 12 principles along with other agile content.
Its interesting that the author started to point out that companies who have been tackling the agile process have been producing crap results in terms of code.I guess only people who know how to agile should use it or as the author calls them professionals. Describing how the work environment between two companies can tell how professional they are with organizing and that comes clear with being agile.
Dan's Tech Rant 