Not actually counting all the bolts after replacing the window on the plane; not checking in with the supervisor before administering that drug; not double checking that the name on the ID matches the name on the passenger list...
And signing something off with someone else’s supervisor code goes well beyond cutting corners on a process, though - that’s falsifying records. At that point you’re subverting the process.
Sure, some approval processes are BS, but... generally, any time you’re in a role where you need a supervisor to sign off on stuff, you do not know enough about what matters to your business to tell the difference between BS and critical safety or security guarantees.
I suppose put it this way. Imagine a software developer slipped in smaller code changes and circumvented procedures like QA or code review because they though it was "just some minor thing" Would you find that OK?
We all know there are bad or stupid rules out there. But honesty's not a rule, it's more of a moral principle. Gray areas for sure, but when dishonesty becomes a habit, or makes one lose trust, or actually breaks a rule meant to prevent an issue, it's a problem.
.
> I am not always honest,
I work with regulated professionals. Honesty is a big deal. Dishonesty is seen as a fundamental personal flaw. Healthcare professionals who've been dishonest struggle to show remediation.
It's really weird to me that I need to explain that forging someone else's name on documents is a bad idea.