Yellow Brick Code: Lessons from The Wizard of Oz on Enhancing DevEx
summary
Claims concrete wins and real failures: an early Backstage rollout fails for timing and front‑end/ownership gaps despite contributed plugins; custom frameworks accumulate tech debt; CI/CD and repos are instrumented by piping GitHub audit logs into BigQuery for measurable friction; a survey names lack of documentation and reorgs as top pain points; platform work replaces pull‑request gatekeeping with automation and self‑service; standardization cuts cloud sprawl from seven providers down to 1.5 cloud providers, improving cross‑team onboarding and velocity.
AI-written summary · about
chapters (11)
- 0:00Yellow Brick Code and DevEx
- 1:49Tech debt at Travago
- 3:38Local optimizations
- 6:54Meeting Scarecrow and Tin Man
- 9:50Resistance to change
- 14:29Myth of all-knowing solution
- 16:14Learning from mistakes
- 18:02Industry guidance insights
- 21:18Reflecting on goals
- 23:22No silver bullet
- 24:46Closing thoughts
related talks
36mDeveloper Experience : From Hype to Reality
27mLessons from a Year with Backstage: What Worked, What Didn’t...
20mLife after The Chocolate Factory
54mDeveloper experience platforms
52mPaving the Road to Effective Software Development
07mDeveloper Experience can drive business growth
21mImproving your Developer Experience Through Platforms and Generative AI
31mAgility, Craftsmanship and Cargo Cult: What's the Link?