Paved roads to hell: Antipatterns of platform engineering efforts
summary
Internal developer platforms often become a single bottleneck when built as infrastructure first not product work, with concrete antipatterns: work as imagined vs work as done (disconnect from stream-aligned teams), forcing adoption via management, and treating platforms as lax production services. Remedies he gives are specific: use the community, dogfood the platform by embedding platform engineers in stream teams, expose code/repos and docs for contribution, fix real friction points rather than mandate use. An unusual note: “auditor hallucination” warns against phantom compliance fixes.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 0:30Field of Dreams
- 2:34Developer platforms
- 3:10Vocabulary
- 3:54Internal Developer Platform
- 4:45IDP
- 5:33Paved roads
- 6:33Work as imagined vs work as done
- 7:02Cabin crew
- 7:44Work has done
- 9:05How to go about it
- 10:06Community recognition
- 10:20Worlds first written complaint
- 11:34Listening
- 12:13Unblocking yourself
- 12:46Advocacy
- 13:09Support channels
- 13:35Management influence
- 14:40Build for the majority
- 15:32Road to hell
- 15:44Outro
related talks
45mPlatform Engineering: A Deep Dive Conversation
48mSome Principles From Real World Internal Developer Platform Engineering
37mPlatform Engineering's Inferno
25mCommon platform team mistakes and how to avoid them
49mBeyond Engineering: The Future of Platforms
34mPlatforms: Defying the laws of IT physics
39mPlatform Engineering as a (Community) Service
44mPlatform Engineering is All About Product