Keeping your codebase fun at scale
summary
Claims a repeatable three-step process — measure developer happiness with a survey every three months (1–5 per codebase), write a concise front-end vision, then prioritize one long-running dev-ex project at a time. Implements small tasks, a dedicated developer-ex team for cross-cutting work, and progress tracking via spreadsheet plus an internal web tool and simple CLI that lists files using deprecated code. Reports improved front-end scores after focused quarters.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:05Unfun codebase signs
- 3:10Fun codebases proven
- 3:52Measuring dev experience
- 5:39Vision for improvement
- 7:01Prioritizing work
- 8:27Tracking progress
- 10:37Q&A
related talks
01h 01mDoes Your Codebase Spark Joy?
15mEstablishing Platform Teams to Utilize the Economy of Scale
43mScalable Best Practices for Your Development Team
58mDeveloper Joy – How Great Teams Get S%*t Done
34mBuilding a Culture For Developer Productivity
28mSome small steps for code, One giant leap for quality
26mEnhance Developer Experience by community
24mBetter software faster