Do We Need Software Craftsmen?
summary
Argues that software craftsmanship extends Agile by shifting focus from projects to people and long‑term code health, extracting three concrete values: passion, quality, and the will to learn. Recommends concrete practices: test-driven development, continuous integration, pair programming, mob‑design sessions with one PC that run successfully for seven years, and aggressive refactoring to avoid technical debt. Cites specifics: 13 years as a developer, started TDD in 2005, debugger use drops to about once a month, and an 11‑year legacy project that survived through these practices.
AI-written summary · about
chapters (7)
- 0:00The case for craftsmanship
- 2:18Cultivating passion
- 3:47Prioritizing quality
- 9:44The importance of learning
- 12:43Refining the philosophy
- 15:53Conclusion and closing
- 17:11Questions and answers
related talks
39mSoftware Craftsmanship
49mExtreme Professionalism - Software Craftsmanship.
01h 01mKeynote: Software Craftsmanship – Growing a Technical Culture
44mA Plea for More Software Craftsmanship
47mSoftware Craftsmanship, What Is It?
45mBeyond Craft: Revisit Your Relationship with Software Craft
50mSoftware Craftsmanship - A Tale of the Soft Duties of a Programmer
37mBeyond Software Craftsmanship