Early in my career, I was a systems engineer for an airline. My boss gave me one of the most valuable briefings I have ever received.
“If you f*** up, come tell me immediately. I do not care how bad it is. Come tell me and I can help you fix it. But if you try to cover it up, you will fail. It will create more problems, more damage, and eventually it will break something important. And here is the part you need to understand. All the data will be in the logs. I will find out who f***ed up, and I will, let me repeat this, I WILL throw you under the bus. So save yourself the trouble and just tell me when you f*** up.”
At the time, I thought it was just a funny, aggressive way to say, “Please communicate clearly.”
It was not. It was survival advice.
Not long after that, I was asked to remediate a vulnerability against the airline’s booking site. The issue was HTTP CONNECT. Basically, do not allow HTTP CONNECT to the booking engine.
Whatever. I got this.
Keep reading
I wrote an iRule, blocked it, tested it, fixed it, dropped the mic, and walked away like I had just personally saved aviation from cyber doom.
About thirty days later, we had a four-hour outage. The booking engine went offline.
Why? Because some dipshit decided it would be a great idea to log LOCAL every blocked HTTP CONNECT request.
That dipshit was me.
The logs crushed the system. The fix became the problem. I had taken a vulnerability remediation task, added a little “look how responsible I am” logging, and accidentally built a self-inflicted denial-of-service machine pointed directly at the booking engine.
That is a special kind of professional nausea. The kind where your stomach drops, your face gets hot, and your brain immediately starts opening tabs it should not open.
Maybe it was not me. Maybe something else changed. Maybe the system was already fragile. Maybe we should blame capacity planning, Mercury in retrograde, or the general sins of commercial air travel.
But the logs were there. The evidence was there. And the truth was there. I f***ed up.
That moment burned the lesson into me permanently. Failure is not theoretical when customers cannot book flights. It is not a leadership quote on LinkedIn with a sunset behind it. It is real. It has impact. It has cost. It has names attached to it. And sometimes one of those names is yours.
That policy from my boss rewired my nervous system. It turned shame into speed. I stopped wasting energy on spin and started using that energy on recovery. I stopped trying to protect my ego and started trying to protect the system.
And in sales engineering, that muscle matters. Because you are going to get it wrong. A demo will crash in front of the CIO. You will give an answer with full confidence and then realize later you were confidently driving the wrong car down the wrong freeway. You will tell a customer something works a certain way, then find out there is an asterisk the size of a Buick sitting in the documentation.
The clock starts the moment something goes wrong. Not when you feel emotionally ready. Not when you have crafted the perfect executive-safe paragraph. Not after you have quietly hoped the problem dies in a corner like a houseplant nobody watered.
The moment something breaks, you have a choice. Own it or hide it. Owning it feels bad for five minutes. Hiding it can poison the whole deal, the relationship, and your reputation.
The best move is almost always the same:
Here is what happened.Here is the impact.Here is what I know.Here is what I do not know yet.Here is what I am doing to fix it.Here is where I need help.
That is not weakness. That is professional adulthood.