The code etymologist
summary
Argues that writing docs is fine but moving key facts into executable code prevents rot: enforce Node version with package.json engines + .npmrc enforcement, validate 200+ env vars at startup so the app crashes with explicit errors instead of mystery failures, and describe payloads with enums and discriminated unions then validate them with Zod runtime schemas with TS inference so runtime values and compile‑time types stay in sync.
AI-written summary · about
chapters (22)
- 0:00Code etymology introduction
- 2:50Code etymologist role
- 3:12Why documentation is often missing
- 5:43Documentation types needed
- 6:03Self-documenting JS setup
- 7:08Node.js version consistency
- 9:14Challenges with written docs
- 9:36Moving versions into code
- 11:02Safe env variable management
- 12:25Type-safe environment variables with Zod
- 14:10Code better than docs
- 14:31Understanding data structures
- 15:57Limitations of untyped JS
- 17:20Enums for type definitions
- 19:47Discriminated unions
- 22:37Runtime validation and types
- 23:19Schemas for safety
- 24:44Longer code meaning
- 25:05Further learning resources
- 25:27Docs as source of truth
- 26:11Preventing future etymologists
- 26:54Call to action
related talks
30mRefactoring large JavaScript codebases
35mThe Social Coding Contract
19mStop writing code
34mNot Your Uncle’s Clean Code (TypeScript Edition)
22mThink you know TypeScript? Think again.
49mTypescript. Runtime. And in Between.
50mThe Code is Documentation Enough
47mEverything I know about writing quality software