How an API helped me change my Perspective of FAILING
summary
Triggers a wrong API in production via Swagger and sends a welcome email to 400 German users the night before rollout, creating a potential adoption and reputation hit. Team mitigates by sending an apology email, revoking wide prod access, adding pairing in prod and a test tenant, improving documentation and post-release strategy. Recovery takes weeks of trust rebuilding; operations reframes it as a success after safety nets prevent repeats.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 0:20About Jaya
- 1:11Why should I talk about failing
- 3:34The Story
- 9:04Failures are Perspective
- 9:36What happened
- 11:00What we did
- 12:33Learnings
related talks
09mWhen I broke production, and it almost broke me
28mHow To Finish What You Start: Lessons From Actually Shipping..
39mConfessions of a Systems Engineer: Learning from My 20+ Years of Failure
32mMy Great Awakening: Top “Aha” Moments As Former Dev Manager
22mYou didn't fail, your product did.
29mEmbracing Failures to Avoid Meltdown
49mHow to tell people they failed and make them feel great!
40mUnlocking the secret to success in the API Economy
