Embracing Failure
summary
Argues that repeated small prototypes beat chasing a mythical “code hero,” demonstrating tools and results: a failed box2d physics experiment that pivoted into a creepy hit, a procedural music generator seeded from musical scales that drew one listener three hours a day, and Edison’s “10,000 ways it cannot work” framing for learning. Recommends keeping a diary or blog to measure incremental progress, deliberately doing cross‑discipline experiments to desensitize fear, and quitting or open‑sourcing dead projects to avoid burnout after a near‑paralyzing episode.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:31Embracing failure Soledad Penadés / @supersole
- 3:14Why is this happening?
- 4:27Everyone wants to be a code hero
- 5:00Massive dissonance
- 5:32This is awfully unhealthy.
- 6:24So what's the difference between you and a "hero"?
- 6:36We leam from failure
- 7:47We don't compare with others
- 10:01We build many things
- 11:16We are not afraid to give projects up
- 12:07We don't fear the unknown
- 14:47We welcome errors
- 16:23We might intentionally look for errors
- 17:22We also laugh at failure
- 19:09Conclusions
- 19:29Care for yourself.
