How To Be Happy Being Average
summary
Argues that small teams should stop copying Netflix/Google and focus on metrics-first choices that actually fit limited people and budget, showing a concrete win: instrumenting a broken Rails app with basic response-time and query metrics leads to measurable fixes. Recommends simple time-series tooling like time-series Influx and clear alerts with intent documented — example: a 50% alert made sense only with the disclosed three-node capacity and disaster plan, not as raw panic.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:30Meet Katy Farmer
- 1:15Katys Family
- 2:43Obstacles
- 3:14Tools
- 5:20Average
- 6:20Big vs Average
- 7:42Insight
- 9:04Metrics
- 10:28Communication
- 15:13Optimization
- 15:44Conclusion
related talks
38mSimplicity: The Key to Software Success
32mIn a Land before Metrics
47mThe dangers of focusing on output vs outcome
22mHow to be an inefficient developer?
20mHow to keep everyone happy (on a shoestring)?
20mScale up your job satisfaction, not your software
45mOne size fits all! Not at all!
05mBe Moar Ridiculous