Good Code: What, Why, and How to Get There
summary
Argues that the single most important property is readability because consultants and new team members must make fast, correct changes; recommends automated formatting (IntelliJ/Visual Studio), meaningful names, small scoped methods, guard clauses and extracting technical details into libraries so the narrative stays visible. Advises no paragraph-length comments, no magic values — use named constants, avoid reflection and out parameters, be wary of premature architecture (author cites ~90% of planned flexibility never needed; one car maker sold 250 units).
AI-written summary · about
chapters (43)
- 0:00Introduction
- 1:22What is good code
- 2:23Why is it readable
- 2:44Usability
- 3:07Common Case
- 3:57Business Case
- 4:55Technical Quality
- 5:48Fast
- 6:02Fast isnt an issue
- 7:16Vacati
- 7:45Corolla
- 8:40Outline
- 9:05Personal Story
- 10:44White Space
- 11:45Whitespace
- 12:39Narrative
- 13:59Comments
- 15:40Example Comment
- 17:11Bug Documentation
- 17:52Logic
- 18:53Details
- 19:19What does this do
- 20:35Why would we want you
- 21:26Interview moment
- 22:14Make logic visible
- 22:51Looking for tickets
- 24:28Implementing algorithms
- 24:38Separate methods
- 25:21What abstraction means
- 25:36Sample code
- 25:53Technical details
- 26:29Complexity
- 27:28Cleverness
- 30:07Cut and Paste
- 30:40Named Constants
- 31:22Architecture
- 31:56Control Flow
- 32:12ObjectOriented Paradigm
- 33:14Multiple Return Points
- 33:33Multiple Methods
- 34:16Complicated Stuff
- 36:21Multithreading
- 37:10Extra Flexibility
related talks
20mGood Code is a Balancing Act
59mTechniques for writing high-quality code
54mReadable Code: The Secret to Clean, Productive Software
53mIntentional Code - Minimalism in a World of Dogmatic Design
17mReady for Readable Code?
39mYou should stop writing code
50mThe Art of Clean Code
50mThe Code is Documentation Enough