Operational Excellence in April Fools’ Pranks: Being Funny Is Serious Work!
summary
An operations playbook for April Fools pranks: deploy behind feature flags so you can flip off a broken prank in minutes, use browser JS to run dark launches (start at ~1% and ramp up) to reveal scaling bugs before launch, load test for sudden jumps (Stack Overflow’s “stack egg” overloads balancers at 10:23 UTC then gets disabled in 3 minutes, full recovery in 30), involve support/PR/sales, and write a company-wide post-mortem.
AI-written summary · about
chapters (4)
- 0:00Introduction
- 3:45What Makes an April Fools Prank Funny
- 7:18What Makes an April Fools Prank Not Funny
- 15:20What Makes an April Fools Prank Lazy
related talks
06mPrankOps Automate Your Memes
49mHow to get smarter while doing your job
48mPerformance culture through the looking-glass
31mPixels, Promises, and Panic - Horror Stories of Production Nightmares
04mPrioritising the tricky stuff when building your platform
44mLizard Optimization
40mDistilled Abnormal DevOps Iterations
16mShift Left, Not Off a Cliff: Why Your Testing Strategy Is Breaking Developers