The End of Fun
summary
Argues that creativity and play measurably improve software and shows concrete habits that produce that: red‑green‑refactor as a deliberate closed↔open cycle, weekly one‑hour retros to inject creative time into the story mill, paired programming at Pivotal style. Gives numbers and outcomes: RailsBridge runs hundreds of events over four years and introduces several thousand people to Ruby; ~150 pairing partners observed; large firms like HP IBM GE and old successes (Twitter at 12 engineers) push growth pressures. Ends with a real test: teams that keep ping‑pong and retrosship maintain speed and quality.
AI-written summary · about
chapters (11)
- 0:00Welcome
- 2:25Who I am and my background
- 5:15Ruby’s growing pains
- 8:23Growth kills creativity
- 10:48Myth of creative archetypes
- 13:14Open vs closed thought
- 16:45TDD and creativity
- 20:57Creativity and luck
- 24:08Retrospectives as space
- 26:12Refactoring for creativity
- 28:56Keeping fun alive
related talks
26mUpdate your team to be more extreme
31mKeep Software Weird
31mThe Effective Developer - Work Smarter, Not Harder
01h 00mThe Influential Software Engineer
49mExtreme Professionalism - Software Craftsmanship.
13mRailsConf 2011: Corey Haines
10mMicrotalk: Working with Rubyists
27mThe Many Ends of Programming