DX for 10x IaC: The Force Awakens
summary
Platform team uses hand-drawn architecture sketches, calibrated questions and tiny Confluence how‑tos to tame CI/CD and choose tooling; a forked Python DSL competes with Helm vs Python DSL and community input plus repo maintainer calls decide the direction. Policy tooling research surfaces Kerno. Migration plan runs discovery and collaboration sessions for 120 developers and 400 services, creates a documentation feedback loop, and yields higher adoption and fewer surprises (auto‑deploy was rejected by some teams).
AI-written summary · about
chapters (6)
- 0:00Introduction and journey
- 3:19Learning new tools and systems
- 9:05Shifting to internal developer focus
- 16:49Collaborating with the community
- 20:45Becoming the force in DevOps
- 25:01Key takeaways and conclusion
related talks
22mDX for Internal Teams
31mDX to another level
12mKeynote: DX Is the New UX: How Technical Friction Impacts Business Value
27mYellow Brick Code: Lessons from The Wizard of Oz on Enhancing DevEx
26mTransforming Developer Experience The Good, the bad and the ugly
53mCode Foresting: Automating Architecture Governance for .NET Teams
26mScaling Better Software Delivery: A Framework for Dev Enablement Through DevRel and Outreach
42mBuilding DevX Teams, my story