Leading With The Platform: A Platform Engineering Approach To Tech Debt
summary
Platform team converts on‑call symptoms into proposals: trace shows slow deletes, a library upgrade reduces DB CPU and forecasts a 10x capacity gain; project gets pitched with ARR forecasts, customer mix, per‑service load models and a scaling roadmap. Results: by end of Q1 a quarter of projects are in progress, another quarter scheduled, some completed, half of engineering engaged, work in OKRs and product gives no pushback — the plan works.
AI-written summary · about
chapters (5)
- 0:00Introduction and speaker intro
- 1:46What is platform engineering
- 7:27Tech debt pitch on a dev team
- 18:34Scaling roadmap for engineering
- 27:00Key takeaways and Q&A
related talks
23mPlatform Engineering for Architects - Crafting Platforms as a Product
47mPlatform Engineering is Domain-Driven Design
48mPlatform Engineering is Domain Driven Design
24mSignificance of Platforms in Product Development
32mPlatform Engineering for Software Developers and Architects (Redux)
15mWinning the Case: Convincing Your Product Manager to Prioritize Technical Debt
30mProduction › Prototype: How a Small Team Replaced a Core Platform in 90 Days
46mManaging architectural debt in a hypergrowth context