Convergence on Platforms
summary
Argument: companies inevitably converge on platforms to reduce cognitive load and speed delivery. Evidence: teams experimenting with Node.js + CircleCI vs Kotlin + AWS vs Scala + Jenkins and Kubernetes creates knowledge overhead; building a central platform cuts that. Practicals: hunt shadow‑ops, track adoption/diversity/impact metrics, stabilize observability, prioritize quick wins on current tech. Pitfalls: rebranding roles into new silos, building platform features too early, or taking 1–1.5 years to ship a big platform. Example outcome: built a feature‑flag tool then replaced it with SaaS.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:2780s/90s software development
- 3:54Waterfall to agile shift
- 6:22DevOps rise and limits
- 8:49Modern org flaws
- 10:16Convergent evolution
- 12:03Tech stack dangers
- 14:08Standardizing platforms
- 16:13Platform success metrics
- 18:22Abstraction vs illusion
- 19:25Platform pitfalls
- 21:28Building via feedback
- 23:13Measuring platform impact
- 24:16Prioritizing stability and incremental improvements
- 25:19Human factors in change
- 26:00Documentation best practices
- 27:03Platforms as products
related talks
46mBeyond DevOps: How and Why Companies Converge on Platform Models
26mThe common fallacies on platform building
47mPlatform Team Structures and Concerns
50mWhy Your Platform Monolith Is Probably a Bad Idea
39mPlatform Engineering as a (Community) Service
25mPlatform Engineering: Evolution or a Fancy Rename?
41mPlatform as a Product
27mWhy Developer Platforms and a curated Dev Experience are a must have when scaling