Alright, I got a question: as a beginner, how so you identify that when something goes wrong with a product, that it was your fault? My boss just Slacked me that one of the websites we're working on has a problem where the buyers can't place an order because I allegedly used the wrong database table. Which I don't remember doing. But maybe I did.

@azuredivay So it's a norm for devs to just take everything that goes wrong, even if it's not their fault?

@azuredivay gotcha.

You're going to break a lot more shit in you career, if you're worth a damn as a developer. Never worry about who's to blame, and just focus on fixing the challenge presented. Those who look for someone to blame are largely ignorant to the problem and the solution.

"Move fast and break things" - words to live by (in most cases)

I've found that most management personnel want someone to blame, but more importantly, they want a resolution. Find the problem, fix it, and if you report back with a plan to keep it from happening again, they'll be thrilled.

Not always the easiest thing to do, especially in the cases where someone else made a mistake... But, it definitely leaves a good impression.

Boss don't slack people because of a single mistake. More like they wanted to slack you for a while and they finally have a reason.

There is 'git blame' to remember whether it was you or not. And I'm working (and mostly worked) at company where my boss is just a colleague with more paperwork to do and stronger voting rights.

@burswag what @azuredivay said. Accept no blame off the bat, go investigate and fix, then let them know why it broke, how you fixed it and how to prevent this happening again. You don't even need to place any blame.

My boss said he already fixed it anyway.