Founder at bluen.io
Last night I burned $600 on a dumb one-line bug.
I was tweaking and updating my system late at night. Tired, not paying the attention I should have, and that's exactly where it went wrong: I took down my own service and impacted my clients.
The worst part wasn't the money. It was knowing the mistake was completely avoidable, and that there were people on the other side counting on my system being up.
Two lessons the hard way: never push to production late and tired, and always have a fast way to roll back when something breaks.
I want to hear from you: who's taken down their own service with a silly mistake? How did you handle it in the moment, and what did you change so it wouldn't happen again?
Engineering leader by day, indie dev by night. Process obsessive by necessity — 20+ years in high-stakes regulated software will do that.
Welcome to the club. We have jackets.