From Horror Story to Fairy Tale: Writing Code
summary
Argues that developers spend 10:1 reading to writing and that clarity saves onboarding time and bugs; shows Daily WTF examples of bad dates, double negatives, and brittle CSS class names; recommends concrete fixes: a code review checklist, consistent vocabulary and spell‑checking, deep namespacing, and using semantic tags and explicit verbs; cites turnover (average job change ~2 years, 4 years a high‑water mark) and says simple measurable steps cut maintenance cost and make code testable and accessible.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:23Software Design Goals
- 2:00Activities
- 9:52Onboarding
- 11:56Accessibility
- 14:53Ambiguity
- 19:16Semantics
- 20:03Vocabulary
- 23:09Disambiguation
- 24:22Ephemeral Use
- 31:42Architecture
- 40:42Namespacing
- 41:43Code Reviews
- 43:04Summary
related talks
43mClean Code: Be The Hero
54mReadable Code: The Secret to Clean, Productive Software
42mWriting Code for Humans, Not Computers
34mHow do our ideas about coding affect the software we create?
39mYou should stop writing code
43mClean code, is it really worth it? A story about monsters and...
15mWrite Less CSS
40mGood Code: What, Why, and How to Get There