Unfortunately, most people who break things while they make changes will swear up and down that their change didn’t break anything.
I find it worse when they swear that they didn’t do anything at all. The changes just happened spontaneously.
Those people are almost as bad as the junior devs that are very confidently incorrect.
Even worse? Senior devs that are confidently incorrect but are trusted completely because they created an “amazing” VBA macro for Excel 97 once.
Note that this also applies to politicians.
That’s how to make a career. If you never make any mistakes, you’re invisible. Don’t do it too often though, or you’ll eventually get promoted to management.
Oof that’s me 💀
It really depends on the situation. There are times, where it’s better to let it play out exactly like this.
99% of the time though, it’s best practice for me to announce my error, before anyone affected knows what hit them.
I try my damnedest to fix it before I announce it.
“I have owned up to my mistake, and therefore you cannot blame me!”
If it didn’t happen, management may ask what is your value.
I make things go
