You Belong In A Room Full of Wizards
summary
Claim: programmers often “fake it” but still ship working results; evidence: childhood ham radio connects to Japan and Ukraine, shipped a tic‑tac‑toe project that exposed algorithm limits, and real jobs where pragmatic delivery matters more than elegance. Concrete advice: complete code beats perfect code, testing is for confidence not virtue signaling with examples like a project at ~60% test coverage, and practical ways to grow include contribute to exorcism, learn vim/tmux live‑coding tricks, and join open‑source projects such as amber and crystal.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 2:13Myth of self-made expert
- 6:10Early tech exposure
- 10:09Admitting what you don’t know
- 11:32Complete code beats perfect
- 13:19Fearless questioning
- 14:23Learning culture
- 15:51Passive-aggressive harm
- 16:12Fake it till you make it
- 17:15TDD myths
- 20:31SOLID and DRY principles
- 22:36Working with others and empathy
- 25:02What matters in teams
- 26:26Open source contributions
- 29:19Magic in programming
- 31:50Mastering tools
- 33:12Emulating role models
- 34:15Avoiding oppressor mindset
- 35:01Teamwork over heroics
- 37:11Finding team role
- 38:03Overcoming impostor syndrome
- 40:33Open source guide
related talks
01h 12mKeynote: "Am I A Good Programmer?"
40mThe Best Programmer I Know
23mCode and Fear: Talent, Art, and Software Development
43mUnbreakable. Perfect: The Craft of Code
43mJust for Fun: Rediscovering Coding as a Hobby
48mA Personal Philosophy of Excellent Engineering
50mProgramming Intuition
50mHow I'm Becoming a Programmer