Officially made my first mistake
by Onar A.Today I got a notification, apparently, I didn't update the request body on RapidAPI to reflect the latest change 😞. Good thing, an error tracking Sentry reported it so I fixed it before someone else affected.
Lost a potential customer.
Lesson learned!
-
2
You will always do mistakes. What's important is: how much time you need to recover from them and not impacting more people. It's called MTTR (Mean Time To Restore) and it's really important.
In order to reduce it, you need some automation: simple way to put a previous version of your website / database, simple way to manage crisis like sending an email prepared in advance if your server crash, and so on.
-
1
Thanks for the comment.
I added some automation during the development, such as error tracking which notified me right away. Fortunately, the RapidAPI provides a way emailing to a user. So, I fixed the issue and let the user know.I will try to see what else can be automated to reduce even further.
-
-
2
The first of many 😅. The mindset I've shifted towards is less "never make mistakes" (because then you inevitably will make mistakes, and then you beat yourself up for it) and more "how do I minimize the scope impact of mistakes?" (heavy regression testing, status pages, ability to handle rollbacks / replays, etc)
-
1
Thanks for the input
I am glad I implemented an error tracking during the development, it notified me and I fixed the issue, so luckily there wasn't a big impact.
It is amazing how a small overlook may cause a bigger issue.
-