CUPID - for joyful coding
summary
Argues for a practical five‑point checklist called CUPID: Composable, Unix philosophy, Predictable, Idiomatic, Domain-based and shows concrete examples: a test helper ruined by a log4j dependency, left‑pad style npm explosion, gofmt enforcing a single house style, and a 1990s bug fixed by reading clear C code (a > vs >=). Recommends small surface area, observable deterministic behavior and domain‑aligned folders instead of framework‑shaped directories so components compose, are easy to reason about, and actually feel joyful to change.
AI-written summary · about
chapters (9)
- 0:00Joyful coding with CUPID
- 6:29Why CUPID was created
- 13:32CUPID's five properties
- 20:35Composable code and Unix
- 25:11Predictable code and observability
- 32:33Idiomatic code conventions
- 39:54Domain-based code structure
- 44:28Applying CUPID to code
- 55:42Q&A
related talks
49mCUPID For Joyful Coding
55mThe Zen of Programming. A personal journey towards writing beautiful code
57mCore Software Design Principles for Programmers
54mThe Zen of Programming. A personal journey toward writing beautiful code
46mThe Zen of Programming. A personal journey towards writing beautiful code.
51mEmbracing Simplicity
51mTwelve Ways to Make Code Suck Less
20mClean Concise and Collaborative Code