Reviving the art of software design
summary
Twelve JavaScript pangram implementations with identical green tests reveal wildly different internal designs, prompting a claim that poor design drives most lifetime cost — typically 75–90% maintenance cost — and shortens feature velocity per Martin Fowler’s design stamina idea. Concrete fixes include constraining tech choices (use a tech radar), practicing on exercism.io and regular book clubs, enforcing SonarQube cognitive complexity and linters as fitness functions, and measuring observability and logging libraries to reduce distributed-system debugging time.
AI-written summary · about
chapters (9)
- 0:00Introductions and overview
- 2:20The state of software design
- 7:51Why software design matters
- 10:01The impact of distributed systems
- 15:04Reasons for the design decline
- 20:25Cultural shifts and prioritizing time
- 24:29Organizational strategies
- 28:27Learning and practice
- 30:47Verifying design and conclusions
related talks
01h 00mEngineering Software
57mCore Software Design Principles for Programmers
01h 01mSoftware Design: Myths and Legends
51mEmbracing Simplicity
46mThe Zen of Programming. A personal journey towards writing beautiful code.
48mThe Effective Software Architect - Work Smarter, not Harder
01h 01mSoftware Design in the 21st Century
55mThe Zen of Programming. A personal journey towards writing beautiful code