Performance culture through the looking-glass
summary
A concrete claim: a Google test raised results from 10 to 30 and page render time goes 0.4s → 0.9s, traffic drops 25% (≈ $2.5B impact), and large brands regress 40% within six months. Teams build RUM infrastructure, CI performance quality gates and dashboards, track P75 P90 P95 distributions, use lab plus field data, set performance budgets, and enforce apoptosis via feature flags with expiries. The surprising numbers, the CI gate that blocks bad PRs, and the operational tooling decide whether this is worth watching.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:00Welcome
- 7:00Performance as a discipline
- 9:00Performance culture
- 11:00Performance maturity curve
- 13:00Performance regressions
- 15:00Reactive teams
- 17:00Lack of continuous monitoring
- 19:00Inconsistent velocity of delivery
- 21:00Tactical management maturity
- 31:00Cultural maturity
- 33:00Continuous monitoring
- 35:00Features
- 37:00Strategic Maturity
- 39:00Cultural Norms
- 41:00Summary
- 43:00Questions
related talks
44mThe 7 Habits of Highly Effective Performance Teams
50mCreating Performance Impact in a Changing Tech Landscape
50mHow to Think like a Performance Engineer
48mThink Fast, First: Empowering a Performance Culture
24mHow To Manage Performance Like a Product
28mEmpowering a Performance Culture
47mHow to win in software development with tighter feedback loops
20mReal metrics for front-end performance