Living your best life as a platform engineer
summary
Built a front-end orchestrator using a monorepo and federated modules that yields 25% faster pages and cuts deploy-to-user time from 15 to 3 minutes; that initial Personio migration succeeds because correct path is easy. A later platform prefetch system forces users into convoluted steps and regresses performance. Current solution collocates GraphQL fragments, composes them upward, uses code generation and auto-linting so route-level composed data enables prefetching by default. Team is nine engineers supporting 500+ daily users, so ergonomics beat cleverness for scale.
AI-written summary · about
chapters (16)
- 0:00Platform engineering life intro
- 1:48Two platform engineering stories
- 10:20Why platform engineering feels different
- 13:30Living your best life as platform engineer
- 14:32Three rules to avoid frustration
- 21:21Lessons from the stories
- 24:36Improving prefetching platform
- 28:35Human relationships in platform work
- 29:18Q&A
- 29:41Career visibility for platform engineers
- 31:48Defining mission in platform and life
- 33:13Overlooked platform investments
- 34:40Managing platform support questions
- 36:04Measuring colleague satisfaction
- 37:09Engineers as users vs regular users
- 38:59Switching to platform engineering
related talks
42mPlatform Engineering in practice — Why and How to start
44mBeyond Metrics: Orchestrating Developer Delight with AI driven Platform Engineering
29mImproving Developer Experience
41mPlatform Engineering for Developers, Architects & the Rest of Us
29mIaC Next Steps in Platform Engineering
29mPlatform engineering maturity - Your key to competitive differentiation
28mWhat's Next in Platform Engineering
25mPlatform Engineering: Evolution or a Fancy Rename?