No, no, no..!
To which we'd add, "and don't go screwing with files you don't understand."
Ben had it EXACTLY right.. whether he deliberately, or otherwise (as here) corrupted (or lost, deleted, etc.) the executable is of no consequence.
The act of breaking a critical function of the org and then fixing it (to become the hero) elevated his standing significantly.
In his case it was a blunder and he was able to recover quite quickly. But, if you're looking for a similar accolade, break it, then fix it (timing is critical here, of course) and it's usually better if you know the fix FIRST.
The content of any technical explanations post-event should be limited and should not necessarily be confused with the truth!
Now, where's that pay rise/bonus?
Biting the hand that feeds IT
