Technical Practices that Take Time but Save Time
summary
Argues that slowing down for practices like red green refactor, continuous refactoring, disciplined code reviews and automating deployments pays off with sustained speed later; recommends TDD when design is known and spike to learn prototypes when it is not; treats code coverage as a “cholesterol” indicator and mentions using PIT mutation testing to probe test quality; advocates collective ownership, small functions, and automated deployment pipelines so changes remain safe and teams accelerate when it matters.
AI-written summary · about
chapters (13)
- 0:00Introduction and value focus
- 2:53What is agile development
- 7:55Feedback-driven and adaptive planning
- 10:03Sustainable speed over velocity
- 13:09Slow down to gain speed
- 19:07Create code with quality
- 27:12Continuous refactoring importance
- 31:29Automated testing culture
- 39:57Code reviews and collaboration
- 44:09Code coverage and design quality
- 51:55Major factors in code reviews
- 54:24Automate deployment processes
- 57:15Investment for long-term productivity
