In any reasonably large team, there is always “someone” who configured that system that is having problems, or made that stupid design choice, or made the last change to that system. Invariably, it’s also true that “someone” was the last person to leave the company.
Thus, the last employee, or freelancer/contractor to depart becomes the “Default Gateway of Blame”
Other posts in the series
- Network Dictionary - Washing My Patch Cables
- Network Dictionary - Coin Operated
- Network Dictionary - Pinch off a Packet
- Network Dictionary - Cloudtard
- Network Dictionary - Default Gateway of Blame (This post)
- Network Dictionary - Negotiable Affection
- Network Dictionary - Reverse Recruiting
- Network Dictionary - percussive maintenance
- Network Dictionary - Powerpoint Waterboarding
- Network Dictionary - Oral Masturbation
- Network Dictionary - consultant
- Network Dictionary - Eye Dee Ten Tee
- Network Dictionary - Moregasm
- Network Dictionary - Blamestorming
- Network Dictionary - velvet rut
About Greg Ferro
Since we have a small team and rarely ever have anyone leave the organization, we’ve loosened the definition to “anyone that isn’t in the room at the time”.
Truer words have never been spoken. It is the fear of failure I believe that drives us to blame others, because if it isn’t our fault, well then, we still appear like we know what we are doing.
This bring up another point. I have observed and even participated in the stupid battles we get in as engineers/admins. I see a tendency to always be right, to always prove ourselves and make ourselves feel superior to others. It is a frustrating thing to see pride get in the way of good work.
This one sounds similar to what I call “Ancient Alien Network Engineer theory”. This describes a situation when one discovers an anomaly on the network which no one knows who did it or why it was done. Similar to Ancient Alien Astronaut theory.