Consumer Driven Software Development
summary
Argues for making every artifact readable by its actual consumer and gives concrete habits: put why in commit messages not just what, name tests with Given/When/Then style so failing 200s show context, prefer long descriptive method names and use Python's __repr__ for unambiguous debugging output. Draws on pair programming and user stories, cites many 10–20 minute naming debates reduced by this mindset, and recommends treating commit bodies and test names as first-class documentation to speed future changes.
AI-written summary · about
chapters (5)
- 0:00Start
- 3:46Extreme Programming
- 5:22The most important language in programming?
- 6:17Consumer Driven Software Development
- 9:48Commit messages
related talks
39mWriting for Humans: Designing better software by keeping humanity in mind
40mBuild Better Software
57mCore Software Design Principles for Programmers
49mExtreme Professionalism - Software Craftsmanship.
53mSoftware Design: Beyond Boxes & Lines
51mEmbracing Simplicity
39mHow we changed our world
50mTactics and strategies on software development: how to reach ...