Sep 22 2020
Leaning Tower of Hangout - noun phrase - The covid-19 quarantine phenomenon in which one discovers a stack of hangouts on one's work calendar, all for the exact same time, all flagged as required, all scheduled while you were asleep the night before.
ref, Towers of Hanoi.
Feb 28 2020
90/10 rule - phenomenon - When 90% of all the stuff management tells you to deploy is monitoring and orchestration software. The remaining 10% is actual make-us-money software.
Feb 28 2020
smoke and mirrors system administration - noun phrase - When you bring a problem to your support team and they go silent for hours to days at a time. No amount of poking and prodding is sufficient to get anyone on the team to respond to your requests for status updates. When they finally get back to you they say that nothing's wrong and you must have made a mistake. Your thing is now unbroken. They never tell you (or anyone, for that matter) what they fixed or how they fixed it.
Jan 14 2020
quantum documentation inconsistency principle - An axiom of corporate life in which there will always be more than one piece of documentation for something, all of the documentation will be measurably contradictory, and none of the procedures will work anymore. See also clandestine institutional knowledge.
Jan 14 2020
clandestine institutional knowledge - The phenomenon in which everybody knows the documentation is wrong and people are so pissed off at said documentation that they don't ever bother to try to fix it. Instead new hires have to play Indiana Jones to find the two people left in the organization who have any working knowledge of the thing and beg to be trained up so they can actually do their jobs. Normally, the newly trained individual doesn't bother to update the documentation, either.
footnote: Most of the time, nobody has the access to update the documentation anymore, which is why nobody ever bothers to fix it.
Jan 10 2020
tumbleweed mode - noun phrase - The phenomenon in which all official support forums for something are either abandoned (no activity for a protected period of time), or any posts that aren't lowball questions (such as "Where's the FAQ?" or replies to release announcements) are utterly ignored (meaning, actual technical support questions).
Dec 08 2019
I'm writing this article well before the year 2020.ev starts, mostly due to the fact that Twitter's search function is possibly the worst I've ever seen and this is probably my last chance to find the post in question to refer back to.
Late in November of 2019.ev a meme was going around birbsite, "Please quote this tweet with a thing that everyone in your field knows and nobody in your industry talks about because it would lead to general chaos." Due to the fact that I was really busy at work at the time I didn't have a chance to chime in, but then an old friend of mine (and, through strange circumstances, co-worker for a time) told an absolute, unvarnished truth of the telecom industry: "Telecommunications as a whole, which also encompasses The Internet, is in a constant state of failure and just in time fixes and functionally all modern communication would collapse if about 50 people, most of which are furries, decided to turn their pager off for a day."
I don't know of any words in the English language to adequately express how true this statement is. He's serious as the proverbial heart attack. For a brief period of time, one solar year almost to the minute in fact, I worked for a telecommunications company in Virginia that no longer exists for reasons that are equal parts fucked up and illegal. The company was bought out and dismantled roughly a year after I escaped by Zander's employer at the time, and seeing as how this was about fifteen years ago as you read this, I guess I can talk in public about it.
tl;dr - If you value your physical and mental health, don't work in telecom.
May 25 2019
Disclaimer: The content of this post does not reflect my current employer, or any of my clients at present. I've pulled details from my work history dating back about 20 years and stitched them into a more-or-less coherent narrative without being specific about any one company or client because, as unfashionable as it may be, I take my NDAs seriously. If you want to get into an IT genitalia measuring contest please close this tab, I don't care and have no interest.
Time was, back in the days of the home 8-bit computers, we were very limited in what we could do in more than one way. Without even a proper reset button or development tools other than the built-in BASIC interpreter if something went wrong there was really no way that you could debug it. If you happened to be hacking code in any serious way on the Commodore chances are you'd shelled out good money for a debugger or disassembler and had at least a couple of reference books nearby. If you were doing everything in BASIC then either you were growing your program a few lines at a time or using some code you got out of a magazine to do low level programming from inside of BASIC (an exercise fraught with frustration, let me tell you). Even then, if something went sideways it was difficult to figure out where you went wrong and fix it. The tools just weren't common at the time. All you could really do was turn off the machine, wait a few seconds, turn it back on, and give it another shot in the hope that the machine wouldn't lock up on you again.
Apr 25 2019
@here grenade - noun phrase - The act of tagging a message @here (meaning, everyone) in a crowded Slack channel (users >= 100), causing everyone who's busy but monitoring to drop whatever they're doing and flame you for bothering them by messaging @here. Normally done by a user trying to get a response to a maximum severity ticket that's been ignored for longer than the SLA.
Example: "PFY threw an @here grenade into the #tech-support channel because the border router was on fire and the admins on call were ignoring their pagers. He got kicked but at least the outage is over."