Developer Productivity at a Developer Productivity Startup
summary
A startup called Reboot.dev runs an eight-person, global team (12-hour spread) that keeps productivity by using parallel async workstreams with a two-hour daily overlap, a generated client SDK for end-to-end types everywhere, and linting of repetition via a framework that auto-persists state. Engineering rules reduce surprises: retries and idempotency, durable execution, and strong consistency (Temporal/restate-style durable workflows, generated clients, TRPC/Stainless examples). LLMs write unit tests but agents are not yet reliable for long unsupervised work.
AI-written summary · about
chapters (7)
- 0:00Intro
- 2:27How to overcome friction in humaning
- 9:01How to overcome friction in coding
- 16:38Nondeterminism in humaning
- 20:13Nondeterminism in coding
- 32:29Summary
- 35:11Outro
related talks
02h 31mDeveloper Productivity Engineering - Extended Session
39mMobile Developer Productivity Panel
52mSurviving the Techpocalypse with Developer Productivity Engineering
32mDeveloper productivity 2.0
20mBuilding High-Productivity Teams Focused on Outcomes: Team Design and Collaboration Case Studies
45mDeveloper Productivity Engineering – The Next Big Thing in Software Development
36mDeveloper Productivity Engineering: What's in it for me?
48mDeveloper Joy – How Great Teams Get s%*t Done