Play with your code
summary
Programming games make three concrete changes: immediate hot reload and visible execution (Exopunks shows each register and file contents) instead of delayed deploys; developer-facing tooling like binding.b for an in-place IRB, live reloading, and LSPs instead of scattered docs; and practical UX fixes—starter templates, ANSI color codes (eight colors that match editor themes), and visual, contained documentation that shows before/after state. The talk names five applyable areas: immediate feedback, color and CLI clarity, documentation, purpose, and autonomy.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:13Programming games vs work
- 6:03Lessons from games for work
- 8:06Immediate feedback
- 10:11Color in dev experience
- 13:40Fun documentation
- 17:49Purpose in daily work
- 19:35Autonomy in coding
- 20:39Q&A








