Extreme Professionalism - Software Craftsmanship.
summary
Argues that overspecialization produces slow projects, low bus factor and blaming, supports collective code ownership and a full‑stack learning path, and cites training 2,000 developers across 40 companies as evidence of practice impact. Recommends concrete practices: TDD and continuous refactoring, automated tests on CI, frequent small releases, and pairing (including ad‑hoc “squeeze the pig” signaling) plus coding dojos (100+ run) to rehearse skills. Promises fewer bugs, easier refactoring and higher team flexibility when these tools and rituals are actually used.
AI-written summary · about
chapters (19)
- 0:00Introduction and welcome
- 1:31History of software craftsmanship
- 4:01Problems from over-specialization
- 12:04Becoming a full stack developer
- 17:19Mastering current technologies
- 20:26Developers as human-machine gateways
- 23:14Agile vs software craftsmanship
- 25:43Software Craftsmanship Manifesto
- 28:30Communication with customers
- 31:41Beyond writing working code
- 32:23Effective automated testing
- 34:07Refactoring and evolving design
- 35:30Code of ethics for software craftsmanship
- 36:36Never stop learning and improving
- 38:20The importance of play and experimentation
- 40:28Pair programming and coding dojos
- 43:14Passion for writing code
- 47:03Solve problems, not just write code
- 48:08Q&A session
related talks
22mDo We Need Software Craftsmen?
01h 01mKeynote: Software Craftsmanship – Growing a Technical Culture
32mSoftware Craftsmanship
39mSoftware Craftsmanship
26mUpdate your team to be more extreme
44mA Plea for More Software Craftsmanship
27m'The Art of Software Development'
33mWhat it takes to become a great developer!