> Not to sound too harsh but if you made the exact same mistake twice (or more!) it's on you. I wouldn't necessarily leap to this. If the mistake is like the o

> Not to sound too harsh but if you made the exact same mistake twice (or more!) it's on you. I wouldn't necessarily leap to this. If the mistake is like the op said (doing something in the wrong environment without realizing) I'd lean more towards a system problem. Why was it possible to do this without realizing? Why is prod the default? Why wasn't there confirmation? Why is there something that relies on peoples memories or undocumented knowledge? When I come across these types of things I fix the system/docs/process. I can only do that because I have the experience to recognize that's the problem, the confidence to call it out, the clout for others to agree (instead of blaming me), and the technical ability to execute. It takes time to build that up, and it's one of the differences between jr and "senior" positions. Sometimes I recognize these situations before but often it's by making a "dumb" mistake, which I still do despite having nearly 20 years experience. I generally don't make the same mistake twice but that's only because I make it so I literally can't.