DevX at Heroku and GitHub
summary
Recounts how get push heroku master and the 12 factor mindset shaped developer-first products, and why Heroku’s early CLI-first design specs mattered. Advises not to over-quantify DevEx, pick a focused cohort and grow from ten to a hundred to a thousand raving fans, and target anchor services and taste-makers. Stresses internal tooling: shorten builds, aim for low cycle time and low mean time to recovery. Predicts more cloud‑native dev environments (Gitpod, Codespaces), richer data tooling (Snowflake, dbt) and better serverless UX.
AI-written summary · about
chapters (11)
- 0:00DevX fireside chat intro
- 1:37Jason Warner’s career
- 3:00Magical DevX tools
- 4:44Heroku’s DevX culture
- 6:50Heroku frustrations
- 8:52DevX lessons for eng orgs
- 11:21Growing with communities
- 13:50GitHub’s internal DevX
- 16:33Justifying DevX investment
- 19:45Future DevX trends
- 21:52Closing
related talks
55mDemystifying “DevEx” and Why It Matters
24mDevEx on Steroids: 🚀 5 Hacks to SUPERCHARGE Developer Experience
50mDevEx on Steroids: 5 Techniques to Scale Developer Experience
42mBuilding DevX Teams, my story
25mDeveloper Experience is central to DevOps success
53mWhere devs are challenged, what devs want and where DevEx is going
54mDeveloper experience platforms
40mBeyond Productivity: Scaling Cloud Dev Environments for Faster Feedback & Sustaina...