Operational Excellence in April Fools’ Pranks: Being Funny Is Serious Work!
summary
Stack Overflow’s “stack egg” prank floods load balancers, causing a self‑inflicted DoS that is disabled in three minutes and fully restored within an hour after a half‑hour rollback and quick fix; recommended tactics are feature flags and dark launches, plus formal load testing, cross‑silo signoffs (marketing, PR, support, execs), and a post‑mortem to capture fixes. Examples include an internal Google mustache rollout and an IPv6 dark‑launch using pixel telemetry; lazy safe options are hosting assets offsite or repackaging existing features.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 4:52About me
- 5:45April Fools book
- 7:14Overview
- 7:38What Makes an April Fools Prank Funny
- 8:09Absurdist
- 8:39Surprise
- 8:50Stache Story
- 10:37Long Story Short
- 13:25What Makes an April Fools Prank Not Funny
- 13:38Punching Down
- 14:58Top 5 Best Practices
- 15:28Feature Flags
- 16:58Load Test
- 18:29Dark Launches
- 20:06Google ipv6
- 22:19Involve all silos
- 23:25Postmortems
- 24:58Sharing knowledge
- 25:45The Grand Finale
- 26:01The Lazy Way
- 26:16Dance Stance Authentication
- 26:41Lazy Technique 2
- 26:51Rubber Ducky Debugging
- 27:50Go Language
- 28:29My Idea
- 29:02The Bad News
- 29:49Conference Talk Proposal
- 30:12Book Giveaway
related talks
01h 02mPractical Chaos Engineering breaking things on purpose to make them more resilient against failure
29mUnveiling Resilience: iFood's Jenga & Sherlock Holmes Practices in Chaos Engineering
27mAll the World's A Staging Server
30mIncident Groundhog Day
30mStorytime with Auntie Aja
32mTesting in Production
36mOops! Learning From Surprise
39m"TestOps: Chasing the White Whale"