Software Craftsmanship, What Is It?
summary
Defines the Software Craftsmanship movement as a reaction to process-heavy Agile/Scrum practices, arguing that teams often neglect the technical, hands-on skills needed to produce high-quality code. Describes focusing on practical software development techniques and professional practice—emphasizing developers who still actively program rather than just produce management artifacts.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 3:301995 - Design Patterns, GoF
- 4:261996 - Extreme Programming is born
- 8:122001 - Teach yourself programming
- 9:222004 - Code Complete
- 11:042008 - Craftsmanship over crap
- 11:212008 - Craftsmanship over execution
- 11:48December 2008 - First .craftsmanship
- 13:29April 2009 - Craftsman Swap
- 14:56May 2009 - The Wandering Book
- 15:50October 2009 - Apprenticeship Patterns
- 16:282009 - The year of user groups and conferences
- 19:48Code? Retreat?
- 21:34December 2011 - Global Day of Coderetreat
- 23:22Productive partnerships
- 24:00Community of professionals
- 25:26Steadily adding value
- 27:21Well-crafted software
- 28:46Up, practice, practice
- 31:15Code Kata
- 33:00Alone
- 34:30Or in a group
- 36:31But I want to do something real
- 38:57Reading foreign code
- 39:24Writing tests
- 40:20Refactoring old code
- 41:12Documentation
- 42:22Building something real with TDD
related talks
37mBeyond Software Craftsmanship
22mDo We Need Software Craftsmen?
39mSoftware Craftsmanship
44mA Plea for More Software Craftsmanship
45mBeyond Craft: Revisit Your Relationship with Software Craft
01h 01mKeynote: Software Craftsmanship – Growing a Technical Culture
13mCraftsmanship unraveled
45mCrafters in 2018: Revisit Your Fundamentals