Developer Experience : From Hype to Reality
summary
Case studies from Rabobank and Bol.com show concrete practices: measure time to first hello world to track predictability, automate infra and DevSecOps (OWASP guidelines) to cut friction, and use a CLI-based internal developer portal that scaffolds repos, creates protected main branches and enforces four‑eyes. Recommend one knowledge store, one support channel with SLAs and alert integrations, and single work‑item tracking. A real outage reveals backup corrupted behavior when backups live on the same server, proving observability and accountability matter.
AI-written summary · about
chapters (9)
- 0:00Introduction to DevEx
- 1:28Evolution of developer culture
- 3:42Balancing two perspectives
- 7:25Predictability
- 13:51Organizational process design
- 20:09Cohesion and tool integration
- 26:26Accountability in incidents
- 30:32Observability and complexity
- 34:15Conclusion and takeaways
related talks
54mDeveloper experience platforms
39mDeveloper Experience: How to Conquer the Hearts of Developers
25mDeveloper Experience is central to DevOps success
35mBuilding Effective Developer Experience
50mDevEx on Steroids: 5 Techniques to Scale Developer Experience
20mDeveloper Experience Is Central to DevOps Success
44mHype Driven Development
41mPrinciples of developer experience