Table of contents
No headings in the article.
Picture this, you suggested an idea to the team. Your manager loved it, praised it. Gave the green light to write up the code and deploy. You spent an entire work day on this, tested on different platforms, browsers, different environments as you typically do. Then you ship it.
You feel good! End of the quarter performance review is coming up, this would look good for you.
Then boom! Customers are screaming - bugs, can’t login. Can’t breathe, what’s going on?? You panic!
Should you disappear, cry? Change numbers, name, countries, run away??
Nahh you suck it up and handle it like a big boy (or gal!) own up, ship a fix for an edge case you could have never imagined - how in the world is a user able to log in and not have a userID. Huh.
But you can’t point fingers, it’ll look even worse.
Now you’re contemplating whether to bring this up in your end of quarter performance review. Idea was great, but not execution… what should you do?? Decisions decisions…
Finally, you decide to include it as both a win and a lesson because you are a developer and this is your everyday life,
Not shipping bugs to production hopefully but your users interacting with your product in ways you could have never imagined, now you are reminded to constantly be on your toes, thinking miles ahead of your users. It’s the only way to win.
Embracing the failure and learning from it.
Also, embrace ErrorBoundary, it’ll save your dignity.