How we revolutionized developer experience with 3.5 Platform Engineers
summary
Three and a half platform engineers transform developer workflow for ~30 developers at Kognic by shipping three cloud‑native solutions: ExternalDNS (two weeks to migrate, removes DNS ticket bottlenecks with Cloudflare), cert‑manager (automates LetsEncrypt 90‑day renewals so teams avoid manual secret edits and rolling restarts), and Argo CD (GitOps for declarative kubernetes manifests, resolves ~seven failed deployments/week, restores versioned state). Result: much less manual work on DNS, certs and deployments, initial rollout friction, steady win after four months.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 2:30Company context and challenges
- 5:19Developer experience defined
- 7:25Platform as product
- 11:18Constraints for small team
- 13:48Low-effect magnet approach
- 15:53Strategy for bottlenecks
- 17:37Case study: ExternalDNS
- 23:12Case study: Cert Manager
- 26:43Case study: Argo CD
- 34:28GitOps lessons
- 36:16Impact on rebranding
- 36:57Future plans
- 37:25Q&A
related talks
25mHow We Revolutionized Developer Experience With 3.5 Platform Engineers
31m20k Leagues Under Platform Engineering
33mBlueprints of Innovation: Engineering Paved Paths for a User-friendly Developer Platform
29mImproving Developer Experience
48mCombating the struggles of modern cloud-native java developers
29mSuccessful Cloud Native Platform Engineering – Hype vs Reality
31mPanel Discussion: Platform and Developer Productivity - Trends and Challenges
36mPractical Cloud Native: What Works, What Doesn't