Chapter 1 is about software development in the twenty first century. In the beginning of the chapter the author talks about how you should let your passion determine what you are going to do for your career. He also mentions that just because you have been programming for a long time, doesn’t mean your development skills are going to reflect that. It is very possible that someone who has been working for half the amount of time that you have been working could be a better developer than you. The author also mentions that now days, employers are looking for employees that can do a variety of things, rather than being an expert on one thing. This chapter makes sense to me because I can relate to this in a way. There is a guy i used to work with who has been there for years, but he is by no means the best at his job, seniority definitely is a not good indicator on skill.
Chapter 2 is all about being agile. Over the years companies have been able to come up with agile development practices, based on their needs and requirements. This helps them stay competitive with other companies. He mentions that software craftsman is not meant to replace agile, it is meant to compliment it. A good way to put it is agile helps companies do the right thing while software craftsmanship helps companies do the thing right. This chapter is important to focus on because it defines the differences between agile and software craftsmanship and shows that they are meant to work with each other and are not meant to replace each other.
Site Title 