-2 upvotes, 1 direct replies (showing 1)
View submission: Massive Failure on the Product
Coding is the easy part of the job.
Your tests should have caught this error. You could have saved the project. But you didn’t.
Now with that humble pie out of the way, instead of placing blame and claiming holier than tho.
You can take a second to do some retrospective analysis. What kind of test would have caught something like this? Did I error out in a graceful and informative way?
Comment by AdventurousDeer577 at 28/01/2025 at 10:35 UTC
1 upvotes, 0 direct replies
I'm not sure if you wrote this comment before or after the OP updated his post with the details explaining what happened, but not only this was a backend issue but more importantly he is a junior. It is not expected to be an overworked junior to "save the project".
While I do agree on the general sentiment of your comment (don't blame others and do retrospective analysis), the comment seems unnecessarily obnoxious