Innovating Beyond Hackathons
summary
Argues to replace rare 36‑hour hackathons with recurring one‑ to two‑week intermissions every 6–8–12 weeks so engineers can try risky ideas that may fail but yield real value. Defines Tech Capital (not just tech debt): examples include a crude terminal tool that cuts POC setup effort so sales engineers self‑configure ~80% of cases, and a dashboard that combines open government data to tip sales prioritization — both shipped quickly and improved outcomes.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 3:11Hackathons stifle creativity
- 5:36From hackathons to intermissions
- 10:34Tech capital over tech debt
- 17:41Why try intermissions
- 23:15Cross-functional innovation
related talks
39mStop Focusing on Tech Debt
25mInnovate or keep maintaining legacy
30mEngineering in Overdrive: How to Thrive When Tech Evolution Goes Full Gas
32mMaking an Impact as a Technologist
26mTech debt as innovation, reframing this forever problem as an opportunity
19mEverybody’s Hacking: Participation and the Mainstreaming of Hackathons
01h 02mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World
12mTech debt nomads and slash-and-burn development