The responsible developer
summary
Argues that a responsible developer delivers small vertical slices via a walking skeleton, uses test-driven development plus high-level acceptance tests (Cucumber examples) so refactors safely while preserving behavior, automates build and deployment with CI so every commit produces a deployable artifact and teams keep the build green, prefers simple code and readable tests, practices pair programming and shared ownership, and ships MVPs (skateboard → scooter → car) rather than perfect-but-unshippable systems.
AI-written summary · about
chapters (15)
- 0:00Start
- 0:33How Would You Describe a Responsible Developer
- 5:24Principles behind the Agile Manifesto
- 11:33Walking Skeleton
- 14:19Simple Code Is a Lot Better than Smart Code
- 16:22Mentoring Other Developers
- 22:02Clean Code
- 24:56The Boy Scout Rule
- 27:24Delivering Value
- 28:23Continuous Integration
- 29:38What Do We Want from the Continuous Integration
- 32:17You Should Be Lazy
- 33:17Responsible Developer Is Constantly Learning
- 34:31Tools
- 34:59Use the Right Tool for the Right Job
