Imperfection
summary
Argument claims tasteful trade-offs beat blanket perfection by hitting a sweet spot: Pareto Principle explains why investing 20 percent of effort yields ~80 percent of practical value. Examples: React optimizes for a tree model that works ~95 percent of UIs, image/video lossy compression drops size by an order of magnitude, reason offers a 100 percent sound type system that creates islands of pristine code, BSB compiles changes in milliseconds and a workflow of sed + reformat + compiler pairs 80 tools with 100 checks.
AI-written summary · about
chapters (10)
- 0:00Start
- 5:02Pareto Principle
- 8:23React
- 12:45Constraints Enables Creativity
- 14:403. Adaptable
- 15:391. Badly done 80%: brittle
- 17:372. Hard to Compose
- 18:41Reason Types
- 21:58Trade-offs, Trade-offs
- 27:47Addendum
related talks
40mAssuring top-notch code quality in the Java Universe
31mBalancing New Features While Maintaining Quality
27mDrawing the line between 3rd party and handcrafted code
29mLessons from Zero-Defect Software
20mGood Code is a Balancing Act
30mWhy should I write software well?
10mPractical tech-debt prioritization
53mIntentional Code - Minimalism in a World of Dogmatic Design