The Best Parts! Of My Favorite Things!
summary
Lists concrete judgments not platitudes: walk the Git history to time‑travel commits back to 2010 and inspect decisions, prefer semantic version patterns — get 3.0.1 not 3.0 — because two majors in a row or many patches signal breakage risk, treat infrastructure as code as repeatable auditable setup instead of UI clicks, use grep across hundreds of repos, prefer Postgres for ubiquity, use package managers/Homebrew and npx CLIs, learn systems via Rust borrow checker and TypeScript types, and prefer good error contexts.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:45Reading code
- 4:42Version and API patterns
- 8:32Infrastructure as code
- 10:31Searching through code
- 12:03Writing and editing code
- 16:16Building tools
- 20:40Web frameworks
- 23:44Error handling and containers
- 26:19Favorite programming languages
- 34:36Conclusion
related talks
18m"Good Enough"
39mThings that Matter
40mWhat We Left Behind - 10 Valuable Skills From The 1990s
40mThe Best Programmer I Know
01h 12mKeynote: "Am I A Good Programmer?"
37m10 Programming Lessons From the Past
44mHow do you think when you're coding?
31mThings I Wish I Knew When I Started Playing 'Developer'