Minimalism Driven Development
summary
Minimalism-driven development argues for concrete choices: avoid shipping heavy frameworks—Electron bundles Chrome per app—and inspect hidden baggage like a userland Xbox 360 driver; prefer small libraries or built-in APIs over RxJava for simple async; use Android’s shrinkResources with minifyEnabled and App Bundles (accept managed APK signing) plus a link-check to fail builds on unused resources; account for distribution cost—one gigabyte costs $32 average, up to $75—and skip ViewModel or databases when screens need no logic.
AI-written summary · about
chapters (9)
- 0:00Introduction to minimalism
- 1:54History of minimalism in software
- 6:33Minimalism in mobile development
- 9:25Decluttering codebases effectively
- 13:42Minimalist design principles
- 19:03Workplace minimalism for focus
- 27:52Managing meetings and time
- 31:09Saying no to unnecessary commitments
- 33:16Conclusion and Q&A
related talks
53mIntentional Code - Minimalism in a World of Dogmatic Design
01h 01mGuide to Destroying Codebases the Demise of Clever Code
50mIntentional Code - Minimalism in a World of Dogmatic Design
33mGuide for lazy developer
27mDrawing the line between 3rd party and handcrafted code
17m10 Principles for effective Front-end Development
40mApp Development - Pragmatic Best Practices
37mBuilding Apps that Scale