The Introduction to the textbook sets the goals for the book and the targeted audience.
“One of our goals for this book is to inspire the people who love to create software to stay focused on their craft.”
“This book is written entirely for you—not for your boss, not for your team leader, not for your professor.”
What Is Software Craftsmanship?
The book considers software craftsmanship as some overlapping values, listed here are those values with my thoughts on them.
- Growth Mindset, the belief that you can always improve and find faster, easier ways to do things if you’re prepared to work. Failure should be seen as an incentive to change your approach. “Effort is what makes you smart or talented” – Carol Dweck. I think the growth mindset it very important to quality and success and avoiding burn-out.
- Constantly adapting to constructive criticism and learning to improve areas where you are lacking. This idea is essential to ensuring quality work and keeping up-to-date on the best practices.
- A desire to be pragmatic rather than dogmatic. This important trade-off allows you to get things done and avoid spending too much time making things “perfect”. This ties in well with YAGNI.
- A belief that information is better shared than hoarded. Everyone benefits from shared knowledge which is the basis for the idea of Open Source projects. This allows a greater population to improve shared code and learn how things work.
- Ability and willingness to experiment and not worry about failing, because you are able to learn from the experience.
- Taking control of and responsibility for our destinies rather than waiting for someone else to give us the answer. I think this is basically saying to take initiative, or try to think differently to solve a problem.
- Focusing on individuals rather than groups. This book is meant to help you as an individual improve your skills.
- A commitment to inclusiveness. I think this is a good rule in everyday life but works with being a craftsman.
- We are skill-centric rather than process-centric. It’s more important to be highly skilled than using the “right” process. I think it boils down to it pays to have the knowledge to use your skills in any situation, not having to rely on a template of tools.
- Situated Learning, the idea of learning a skill around those using those skills. Working your first job as a software developer would be a good example of this.
Based on the introduction, this text appears to have very useful information for someone who wants to improve the quality of their work and what they contribute. The book includes good lessons that can apply to any aspect of life. It stresses the idea of improving skills by being open to learning from others, learn from mistakes, and never stop improving.