Establishing Platform Teams to Utilize the Economy of Scale
summary
A front-end platform team claims to keep developer experience healthy while a codebase scales from ~8–10 engineers to 30 and beyond, now over 300000 lines of front-end code. It implements 8-week cycles with metrics (compile times, CI steps, PR latency, TypeScript adoption, bundle size) surfaced via Honeycomb and lucre and GitHub checks, runs an RFC process, weekly changelogs, workshops and 20% ad hoc pairing, and reports that a two-person team preserves shared ownership and speeds improvements.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 0:25Developer Experience
- 1:05Product Board
- 2:14Shared Ownership
- 2:48Frontend Guild
- 4:13Platform Teams
- 5:29DevOps
- 5:50Culture
- 6:14Metrics
- 6:49UX Metrics
- 7:18Lucene
- 7:46Honeycomb
- 8:04GitHub
- 8:52Documentation
- 9:30Alignment
- 10:00RFC Process
- 10:10Open Source
- 10:32Technical Proposal
- 11:30How to gather feedback efficiently
- 12:12How to make decisions
- 13:04Cypress
- 14:00Conclusion
related talks
23mFront-End Platform Engineering
11mKeeping your codebase fun at scale
33mScaling Frontend: Supercharging Productivity with Dedicated Infrastructure Teams
44m5 Building Blocks for Successful Frontend Platform
25mEnterprise Final Frontier – is it possible to change the corporate ways...
28mMind the gap: closing the rift between front and back
35mMicro frontend Has Entered the Game
22mSetting up Enterprise Frontend for Success