Chapter 5 is about heroes, goodwill and professionalism. One of this chapters focuses is the idea of learning how to say no. The author tells a couple stories about how a manager was always pushing for more rather than working with his developers and how that was a unhealthy work environment. Part of being a software craftsman is being in charge of yourself and your own career, this may mean saying no sometimes. But this does not mean say no all the time, because this can be looked as unprofessional. A good manager will put themselves in your shoes to see if what they are demanding of you is reasonable.
Chapter 6 is about working software. This chapter talks about working software and the fact that working software is not enough. There is always a threat of something going wrong later on when the software is not maintained properly and developed properly. Don’t skip steps when you are developing software. This may be hard for some people because deadlines are constantly being forced. If something happens that you are not able to reach a deadline, it is better for you to talk to your manger about it so you are making sure you are producing code to your best ability. I can relate to this chapter because i have fallen in the trap of just producing software that works, rather than taking all of the steps I should be in order to solve the problem at hand. This can lead to a disaster somewhere down the road.
Site Title 