Build Better Software
summary
Argues that better software starts by understanding users and business goals, then balances three measurable constraints: highest quality, lowest cost, shortest time. Recommends concrete practices: map requirements to real user personas, design modular upgradable systems, make code readable, test beyond units, treat security everywhere, and prefer portable stacks (Azure vs AWS). Gives examples: use service workers / PWAs for offline-first fast frontends to cut server load; fix runaway SQL logs that filled disks; deliver weekly in small pieces with users involved.
AI-written summary · about
chapters (5)
- 0:00Introduction to code quality
- 0:38Business goals and software
- 3:24Software lifecycle and design
- 11:47Characteristics of better software
- 25:18Expert interview and best practices
related talks
30mWhy should I write software well?
25mThinking Architecturally
39mYou should stop writing code
47mBuilding software products distilled: customer value, engineering and delivery
38mSimplicity: The Key to Software Success
28mAvoid overengineering & big ball of mud- 7 lessons for maintaining the balance
25mBuilding Castles, Not Sandcastles: Strategies for Software Architecture Success
48mThe Effective Software Architect - Work Smarter, not Harder