The Myth of the Genius Programmer
summary
Argues that lone genius work is rare and costly, showing concrete practices that scale: measure and raise the bus factor by sharing code and decision-making; prefer quick prototype then collaborate cycles so ideas fail fast and learn faster; use code reviews and visible history to turn mistakes into documentation; pick tool defaults (Google Code, distributed VCS, simple auth) that encourage trust; time collaboration to the sweet spot—idea, runnable prototype, invite contributors—so work gets useful adoption instead of languishing.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:05The Myth of the "Genius Programmer"
- 5:18Insecurity
- 9:23Lose the Ego
- 10:14Criticism is not Evil
- 11:52Embrace Failure
- 14:01Practice is key
- 20:36Too late
- 22:08Sweet Spot!
- 22:48Case Study: Subversion
- 24:28Case Study: Ben & Fitz
related talks
01h 02mAround Learning
40mThe Best Programmer I Know
31mThe Effective Developer - Work Smarter, Not Harder
50mThe Effective Developer - Work Smarter, Not Harder
01h 00mThe Influential Software Engineer
49mThe Best Programmer I Know
23mCode and Fear: Talent, Art, and Software Development
01h 03mThe Effective Developer - Work Smarter, Not Harder.
