The Day 2 Hangover: What To Do After the Platform Party Ends - Cat Morris & Nitish Malhotra
summary
Company platform grows from ~50–100 curated modules into 200 components through small forks, creating massive ops overhead. Team introduces GitOps (Argo CD, Flux), infrastructure controllers (Pulumi / Terraform controller / Crossplane) and a backend workflow layer plus Cratics (Centaso) to standardize APIs, enforce policy and auto-reconcile drift. Result: day‑2 costs and manual maintenance fall significantly without a full rewrite, adoption improves by onboarding an exemplar team and recruiting domain producers.
AI-written summary · about
chapters (10)
- 0:00Platform hangover intro
- 1:05Why platform projects failed
- 5:16Root causes of hangover
- 8:03Building platforms without focus
- 9:51Avoiding the platform hangover
- 13:44Choosing exemplar team
- 15:48Curing hangover with GitOps
- 17:36Self-service for developers
- 19:22Recruiting platform producers
- 21:49Summary
related talks
32mOps in the Time of Serverless Containerized Webscale
30mThis is Not a Technology Problem: Leveraging Culture and Process to Make the Most...
27mFrom “No Time For GitOps” To Enterprise Adoption: Selling Flux The Human Way
28mRefactoring Your Team For Fun and Profit
21mDialogue Driven Development
58mKeynote: Seven Habits of a (Mostly) Successful Team
42mA Day in The Life of a Developer Bo$$
15mThe agile leadership mindset: Embracing continuous change as a leader