A Plea for More Software Craftsmanship
summary
Argues that software development should be treated as a craft requiring practice rather than rote coding. Presents two concrete practice methods — the Kata workflow and the Randori workflow — as structured, practical ways to organize regular training for developers.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 3:26Craft versus electrician
- 8:31Software Craftsmanship Manifesto
- 13:10Tools and materials
- 16:20Software fascination
- 17:47Editor as tool
- 21:00Muscle memory and efficiency
- 23:06Editor as extension
- 24:08Training and practice
- 25:32Coding kata as martial arts
- 28:24Code kata structure
- 34:04Randori and team drills
- 36:49Kata projects and resources
- 40:23FizzBuzz kata example
- 42:37Summary
related talks
22mDo We Need Software Craftsmen?
47mSoftware Craftsmanship, What Is It?
01h 01mKeynote: Software Craftsmanship – Growing a Technical Culture
49mExtreme Professionalism - Software Craftsmanship.
39mSoftware Craftsmanship
27m'The Art of Software Development'
45mBeyond Craft: Revisit Your Relationship with Software Craft
37mBeyond Software Craftsmanship