code puce - noun phrase - An IT or ops situation in which the software installed in production is one version and the management system expects a different version. This results in a situation in which everything is running more or less smoothly, and at the same time everything in the monitoring system is going bonkers. Compare with code red, code blue, and so forth.
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).
evolving situation - noun phrase - A situation where, if all hell hasn't broken loose yet it's well on its way.
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.
entropic debugging - noun phrase - The phenomenon in which one can spend weeks on end debugging something using a multitude of techniques, give up in frustration and/or disgust for a couple of days, come back to the project and discover that somehow the bugs have magickally fixed themselves (as verified by diffs and file hashes if one cares to check). The phenomenon is so named due to the second law of thermodynamics, which states that entropy can never decrease, only increase in an isolated system. In other words, as entropy increases overall in the universe it somehow wiped out the bugs in question. See also kinetic pattern baldness.
basketball mode - noun phrase - When a service or application crashes and restarts itself over and over, i.e., bouncing like a basketball every few seconds. Considered an outage.
I haven't actually been on vacation lately, not really. I decided that I needed to go off and do some different stuff for a while. I've been in a rut lately and decided that I needed to shuffle some stuff around. I swapped out the "writing rambling computer nerd blog posts" module for teaching myself a couple of new things and spending some of my downtime offline, curled up with cinnamon tea and a stack of books. Getting away from a screen for a while seems to have done me some good, and I'm almost back up to my old reading pace of five or six books a week. I'd all but forgotten how much dead tree books weigh after the fixed mass of a tablet for so long. The wireless router at home that I set up to replace the astoundingly shitty DSL modem-cum-wireless access point that Annoying, Trying, and Twisted insists we use is starting to act flaky, which suggests that it's reached the end of its functional life, not unexpectedly since this model tends to have overheating problems. A few weeks back I picked up a new router, a Linksys WRT 1200 AC and promptly made a few hardware modifications to it, which is to say I cracked open the case, unbolted the heat sinks, scraped the crappy thermal tape off of the chips and applied decent heatsink grease, and put the router back together. I'm considering wiring a small cooling fan onto the motherboard, maybe on one of the development ports. Lately I've flashed OpenWRT onto the unit and set up quality of service and monitoring so I can keep an eye on things. I'm still working out how to patch it into my exocortex for realtime status monitoring. From a practical standpoint I can install Python on the new router, but doing so leaves next to no room for anything else. I have to think about it some more. I do NOT want to use SNMP if I can help it.
If you thought you were going to escape computer nerd-related rambling, you were sorely mistaken.
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.