Keynote: Software Craftsmanship – Growing a Technical Culture
summary
Claims that over-specialization causes blame and slow projects and presents concrete fixes: adopt T-shaped developers, enforce unit tests and refactoring, run CI so tests run on Jenkins (use Testcontainers if needed), practice with coding katas and book-club chapters, rotate developers, pair/mob program, do weekly “what can I delete” cleanup. Community-building already scales — the Bucharest Software Craftsmanship group reports about 4000 members — and the measurable outcome is fewer patches, faster bug detection, and lower truck factor.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:10The Bucharest Software Craftsmanship Community
- 21:47Software Craftsmanship
- 27:45Replacing Debugging with Testing
- 32:00Invest Time in Training Yourself
- 34:33Unit Testing and Refactoring
- 36:46Culture of Learning
- 39:35Group Code Reviews
- 51:17Takeaways
related talks
22mDo We Need Software Craftsmen?
49mExtreme Professionalism - Software Craftsmanship.
39mSoftware Craftsmanship
44mA Plea for More Software Craftsmanship
45mBeyond Craft: Revisit Your Relationship with Software Craft
27m'The Art of Software Development'
48mThe Effective Software Architect - Work Smarter, not Harder
01h 02mThe Software Craftsmanship