Software Craftsmanship
summary
Argues that Agile rituals replaced technical rigor, causing chronic technical debt and slower delivery: teams add work to a technical backlog instead of refactoring, one developer spends three hours patching with print statements because the system can’t run locally, QA celebrates finding 1,000 bugs, and large projects cost millions yet slow to change. Recommends concrete practices—test-driven development, continuous integration—and reports a 1,300‑member London craftsmanship community and repeated examples where improving code quality restores velocity.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:48Agile Software Development
- 4:18The Agile Hangover
- 14:31Manifesto for Software Craftsmanship
- 22:29XP Practices
- 24:30Mastering the practices is hard ...
related talks
22mDo We Need Software Craftsmen?
01h 01mKeynote: Software Craftsmanship – Growing a Technical Culture
49mExtreme Professionalism - Software Craftsmanship.
47mSoftware Craftsmanship, What Is It?
44mA Plea for More Software Craftsmanship
01h 02mThe Software Craftsmanship
45mBeyond Craft: Revisit Your Relationship with Software Craft
13mCraftsmanship unraveled
