Code and Fear: Talent, Art, and Software Development
summary
Argues that software is a creative practice like art and that most useful code comes from iteration, deletion, and refactoring rather than sudden genius. Gives concrete tradeoffs: Ruby vs Cheese++ as a language/happiness example, bitwise multiply vs simple multiplication to show human vs machine optimization, choosing data schemas and storage constrains features, and using tests, whiteboards and Chrome devtools as actual tools. Claims most written code is “bad” drafts and that polishing makes it useful.
AI-written summary · about
chapters (16)
- 0:00Intro
- 1:08Gift Break
- 2:54Art and Programming
- 4:25Software Development
- 6:33Why is it so hard
- 7:31The version in our head
- 9:31Optimizing for our needs
- 11:27What matters
- 13:00Cheese
- 13:26Who really cares
- 14:52Writing bad code
- 16:08Repeating patterns
- 17:31Imposter syndrome
- 19:13My process
- 20:24Art isautobiographical
- 22:36Outro
related talks
27m'The Art of Software Development'
14mThe Art of Programming
51mThe Art of Software Development
35mCoding: Art or Craft?
31mThe Effective Developer - Work Smarter, Not Harder
34mProgramming with that Disreputable Part of your Brain
11mDeath of a Craftsman: A software developer identity crisis
48mA Personal Philosophy of Excellent Engineering