Opening Keynote
summary
Monzo treats the developer flow as a product: instrumenting pipelines but finding surveys and 30-minute interviews far more revealing than dashboards, then forming a platform team to fix real bottlenecks. Changes include a Jenkins script turned cronbed Go binary to keep staging test accounts healthy, a Slack PR notifier with semantic emoji to cut duplicate reviews, standardizing web builds, moving logs to Elasticsearch and Kibana for usable debugging, and supporting 1500 microservices. Measured satisfaction rises to 78% satisfaction while raw deployment dashboards show little change.
AI-written summary · about
chapters (15)
- 0:00Introduction and theme
- 3:02What is Monza bank
- 5:55Developer experience explained
- 8:05Science behind DevOps
- 11:17Continuous delivery principles
- 13:08Theory of Constraints
- 16:01Creating the platform team
- 19:51Treating developer flow as product
- 23:10User research methods
- 26:03Conducting developer interviews
- 31:07Implementing improvements
- 35:24Measuring impact with surveys
- 38:59Addressing mobile engineer challenges
- 40:44Next steps and platform teams
- 41:26Key takeaways and summary
related talks
46mSharpen Your Tools: Building the right Developer Experience
32mDeveloper productivity 2.0
36mDeveloper Experience : From Hype to Reality
15mKeynote: Creating a Holistic Developer Experience
36mNuances of Influencing Developer Experience and Productivity Through Tech Products
28mHow we do developer productivity at Slack
46mForget Developer Platforms, Think Developer Productivity!
25mCreating Great Developer Experiences with Metrics and Automation.