Clean, Concise, Collaborative Code
summary
Argues for concrete practices: break logic into tiny steps, pseudocode a calculator and catch the division pitfall, move from one giant app.js to separated routers and modules using express.js so swapping a failing DB provider is quick, favor names and small functions, apply dependency inversion, use a testing pyramid (unit → integration → e2e) to gain confidence, and surface decisions in docs; claims teaching at The School Of Code reaches 300+ bootcampers and yields measurable improvements.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:24Planning for clarity
- 12:13Balancing abstraction
- 22:23Testing strategies
- 27:19Documentation
- 33:55Code clear to non-devs
- 37:44Why clean code matters
related talks
20mClean Concise and Collaborative Code
57mCore Software Design Principles for Programmers
31mThe Importance of Clean Code
40mMore Code More Problems
53mIntentional Code - Minimalism in a World of Dogmatic Design
17mReady for Readable Code?
39mRead my code, or why writing readable code matters
19mDevelop, Debug, Learn?