Motorcycles and the Art of Software Maintenance
summary
Argues for pragmatic maintenance: Ruby app uses service objects to move large controller logic into single-call classes, the team of three ships a product used in 150 countries with surprisingly few tests, and the practical worse is better case is backed with concrete examples — WordPress eclipsing Movable Type, Model T economics, and gas engines vs simple electric motors. Positions the duct-tape programmer approach as valid for small teams building working products rather than perfect code.
AI-written summary · about
chapters (13)
- 0:00Start
- 6:00Function?
- 14:54"bad code"?
- 15:24Legacy code.
- 16:24but your users don't know
- 17:54Ruby Code
- 20:04The Duct Tape Programmer
- 22:22A fundamental difference of opinion
- 30:07Rules.
- 30:30Refactor or rewrite time permitting
- 30:54Precision is good. Shipping is best.
- 31:06Keep learning
- 31:20Have fun
related talks
28mAvoid overengineering & big ball of mud- 7 lessons for maintaining the balance
27m'The Art of Software Development'
34mSustainable Architecture
01h 03mTactical Design
51mThe Art of Software Development
46mClosing Keynote
35mCraft, Engineering, and the Essence of Programming
55mThe Zen of Programming. A personal journey towards writing beautiful code