Good Code is a Balancing Act
summary
Argues that strict style rules break more than they help: a university 10-line limit forces fragmentation into tiny helpers rather than clarity, yet the real codebase contains a stubborn 2000-line function that shows the opposite problem. Single-return and single-control-structure rules create awkward nesting or obfuscation. Recommends using interfaces when alternate implementations matter and using IDE refactors to extract an interface. Advises commenting why not how and finding pragmatic balance for readability and maintainability.
AI-written summary · about
chapters (7)
- 0:00Intro
- 2:12The 10 Lines Rule
- 6:21One Control Structure
- 9:29One Return Statement
- 12:22Interfaces
- 14:47Naming
- 16:44Comments
related talks
40mGood Code: What, Why, and How to Get There
57mCore Software Design Principles for Programmers
53mIntentional Code - Minimalism in a World of Dogmatic Design
59mTechniques for writing high-quality code
15mThe Moderate Programmer
18mWriting Quality Code
51mReasons and Ways to Improve Code Quality
53mCode Review - how to do it better?