What Annoys Jeff this Week?

1. Every year around September I opine that there isn’t anything more useless that a formal performance evaluation. Every spring, though, I’m reminded that I’m wrong, because truly it’s impossible to imagine a more pointless “management tool” than the yearly midpoint assessment. It’s all the aggravation of spending time putting paperwork together and none of the remunitative reward of getting a performance bonus. Midpoints are a 100% paperwork drill out of which there’s no significant accomplishment. If I’ve been a turd for the last six months and management hasn’t said anything, they obviously don’t care. If I’ve been an all star for six months and don’t know it, than that’s 100% my own problem. All the midpoint process does is ensure my copy, paste, and update skills are just as sharp as they were a year ago.

2. Last week included new computer day at work. This week has involved a pretty extensive amount of trying to figure out how my own personal workflows will function in a Windows 11 environment. After two days of hunting and hoping and yelling at this computer, I’m absolutely not loving it. In fact nothing is currently working as seamlessly with this new system as it did with the old one. I’m not saying new tech is necessarily bad, just that when the powers at echelons higher than reality decide it’s time to roll it out, they very rarely consider much beyond “ohhh, new and shiny.” I’m sure this will all be functional at some point in the future, but currently it’s causing no end to aggravation. Truly it’s a death by a thousand cuts.

3. Breakfast. This morning breakfast was a “lower carb” everything bagel and precisely two tablespoons of reduced fat cream cheese. Breakfast used to be a proper bagel, slathered on regular cream cheese, a couple of eggs, cheese, and maybe a bowl of cereal. Sure, that’s the diet that has probably killed me, but for starting the day satiated and relatively happy. Look, I know I can’t go back to eating that way, but it doesn’t mean I’m ever going to be fully satisfied with this “reasonably healthful” approach to food.

What Annoys Jeff this Week?

1. Stalled. My quest for more weight loss has been stalled for almost two weeks. I haven’t made any changes from what has worked consistently for the last nine months, but I’ve spent the last 14 days losing and gaining the same pound and a half. I’m trying to be a good sport and going after the 200-pound goal the docs seem to want me to hit… But I’m already sitting at an 1800 calorie a day hard limit and frankly I like eating too much to go restricting that much further. I should also note that I’m prepared to garrote the first person who chimes in and says “you just need to exercise more.” Bugger directly off.

2. New computer day. Wednesday was new computer day at the office. Under most circumstances I’d say that was great. Except the new computer they’ve decided on is a desktop that will live permanently at the office while we take out laptops to live permanently at home. Instead of two work computers it means I now am signed for three separate pieces of equipment. It also means that in order to work between home and the office, I’ll be relying on “the cloud” properly being able to host two decades worth of work product instead of it living on my local drive and simply being backed up to the cloud. I’m not a fan of this for a lot of reasons. Color me curious to see what the response is going to be when our elderly laptops start dying off and someone has to be on the hook for machines that live at home being out of sight and out of mind.

3. Some weeks are busier than others. This one has felt like every time I knock something off my list of things to do, two or three more rise up to take its place. It hasn’t been debilitating, but it has certainly been obnoxious as this trend managed to cross all lines between work and home. It’s the first April in a very long time that hasn’t been entirely consumed by working as an advanced party and event planner. It seems that finally having chucked that one large thing over the side, maybe it’s just a natural effect that 57 small things have come along to eat up that white space on my calendar. 

Failure and recovery…

I was raised in the age of the personal computer. Not long after the first Apple Macintosh ended up in my elementary school’s “computer lab,” one landed on our desk at home. Still, though, I don’t necessarily consider myself a “digital native.” For the most part, my computers have always simply been productivity tools that more or less live on my desk. I don’t generally ask them to do anything extraordinary or heroic – a bit of word processing, web browsing, and video streaming. 

I also have a bit of a habit of keeping my computers just a bit too long. Unlike my phone, as long as the computer is puttering along, I’m mostly satisfied to let it keep going even at a slowed pace. In 30+ years of computer ownership, that’s always been good enough.

Good enough always is right up to the point where it isn’t… which is apparently the point I reached with my 10-year-old iMac last Thursday afternoon. Sometime between when I signed out of work for the day at 4:00 and when I sat down and tried to stream an episode of Game of Thrones while I had dinner at 5:00 (don’t judge me), I suffered what I’ve taken to calling a “catastrophic hard drive failure.” 

If you haven’t lost a hard drive unexpectedly, I don’t recommend it. I’ve spent the last three days slowly putting my electronic life back together. Needing to unexpectedly buy a new computer, of course, just adds insult to injury.

For the last five or six years, I’ve been paying a nominal monthly fee to have my computer backed up “in the cloud.” That has honestly been the saving grace of this experience once I remembered that I actually hadn’t lost decades of photos, writing, finances, and every other kind of file and record you can imagine. Once I got past the initial terror at the possibility of losing everything, getting it all back was just a matter of following all the steps – and downloading a lot of software. 

I’m not absolutely thrilled with my new 24-inch iMac. Stepping down from the 27-inch model feels, in some ways, like a downgrade. It’s a fine machine and I still like the all-in-one form factor, but I’m really missing the extra screen real estate. I won’t rule out needing to add a second monitor at some point to compensate for that. For now, I’m trying to be satisfied with having brough things back to life in fairly short order and without too much trouble. 

For my next trick, I’ll be ordering a new external hard drive so I can start keeping an onsite back up of everything. For most situations that should be more convenient and really cut down the amount of time it takes to recover… but you can bet I’ll keep paying that monthly fee for online backup. It proved to be some of the best money I’ve ever spent on a subscription. 

The most insulting loss of all…

I had a whole post teed up from over the weekend. It should have been sitting here safely waiting on me to do some final edits in Word before dropping it over into WordPress for publication. However, it’s currently not sitting anywhere on my computer. There’s no record that I even edited or saved any documents over the weekend. It’s also not in WordPress. Not in my drafts, not sitting in my scheduled posts file, or anywhere else.

It has well and truly disappeared. And frankly, I don’t have the energy to put into trying to recreate it from scratch.

As of a couple of weeks ago, I’ve officially made 4,000 separate blog posts dating way, way back to February 2010. I say 4000, because that’s how many I’ve written – well, 4,004 including this one. I’ve only made 3,989 of them public. Believe me when I tell you the ones that are sitting there in private mode are some real humdingers. Most of them won’t see the light of day until after I retire, if then. They’re the few examples of times I couldn’t tell the story while obscuring at least some identifying elements slipping through. 

In any case, after 4,000+ posts, you can count on one or two fingers the number of times I’ve simply had one of them eaten whole. That’s the entire reason for my workflow of writing everything first in Word. I don’t expect this to become a common occurrence, but it does mean I’m going to have to take some time coming up with a better failsafe. I’ve got too many things sitting here in various stages of draft to worry that they’re going to randomly start disappearing.

At least I’m not getting paid for this, so all I’ve lost is time… though that may be the most insulting loss of all. 

The last week wasn’t great…

So, the last week wasn’t great times. Personally and professionally there were a lot of moving parts that never quite meshed among themselves or with each other.

Monday and Tuesday I worked from home and all was well, or at least it was well until the storms rolled through, trees fell over, and grid power crapped out and took my access to the internet along with it. No internet means no working from home. Which was a problem because Wednesday was a day where the general contractor was making a big push to get a lot of work done and I needed to be home. Chalk it up to an unplanned day off while the bathroom contractors did their work using generator power. At least someone was getting some work done.

By Thursday morning power and internet were back, but I couldn’t log in to my work computer. After six hours of sitting around waiting for the help desk to get back to me, I was duly informed of the reason why I couldn’t sign in. It seems I was delinquent at completing mandatory annual cyber security training and had been unceremoniously expelled from the network until I took the class, sent in my certificate, and genuflected six times in the direction of the IT office.

Under normal circumstances none of those things would be more than an inconvenience, but there’s a catch. Because of course there’s a catch. Because of reasons, this training can’t be completed from a personal computer. I had to be on the official network, which means I had to schlep in to the office and use someone else’s machine. That’s great, of course, except last week was a steady parade of general contractors and painters trying to wrap up my bathroom remodel. They had full days scheduled on Friday and Monday. With so many more or less unknown elements coming and going at different hours, leaving the house for any length of time just wasn’t something I was willing to do.

The net result between weather and home improvement was burning off three unplanned days of vacation time last week. Adding another 24 hours to the 64 hours of leave I’ve already burned this year to mostly hang out at the house while other people do work. It doesn’t feel like a great way to take the lion’s share of your yearly vacation days.

Yes, I still have a mountain of combined annual and sick leave on the books. If I don’t take any more vacation time, other than what’s already have scheduled, I’ll still carry over the maximum amount allowed, but also means facing the next five months with no impromptu days off. That feels… stifling. I have grave doubts about whether I’ll be able to pull it off no matter how my good intentions.

Breaking in the new equipment…

So, I got a fancy new laptop from work last week. Let me lead off by saying overall it’s a tremendous improvement from the five-year-old laptop I was previously saddled with using. That’s not to say, however, that there aren’t a few issues.

The first, which I discovered on my first full day of using the laptop away from its “docking station” on my desk at the office, is that there are only two USB ports. Those ports are arranged in such a way that it’s impossible to simultaneously plug in my removable Wi-Fi adapter and any other USB device. The adapter is slightly wider than a thumb drive… but sufficiently wide that it makes the second port unusable. Fine. A $13 USB hub ordered from Amazon later (plus $2.99 for same day delivery) and I can now use my air card and a mouse simultaneously. I won’t comment on the aesthetics of that whole set up other than saying it looks like absolute trash sitting on my desk at home. 

This morning, a piece of software I use all day every day fired up as expected and a few minutes later promptly disappeared. It’s as if it never existed on my machine at all. No trace of it anywhere. 

This necessitated a call to the obviously misnamed “Enterprise Help Desk.” The gentleman I eventually spoke to was nice enough, going so far as musing that it was strange because the last person he talked to was having the same issue with the same missing program. More people with the same problem might sound like it’s worse, but in fact being part of a big problem is much better, because something that impacts many users is far more likely to get attention than if you’re the odd man out in the wilderness somewhere. If it’s a group problem, it might actually get fixed. If it’s an individual problem there’s a pretty even shot that your ticket will just linger long enough for someone to mark it complete regardless of whether they’ve solved your problem or not.

Here I am, hoping that I really am part of the many rather than the few. In the meantime, I’ve been directed to the web version of the program that I need to use all day. Honestly, if there’s anything more problematic than not having the software you need, relying on its underpowered web version is it. As always, my standard disclaimer applies… if Uncle wants me to be able to do something, I’ll be given the resource to do it. Otherwise, I’ll cheerfully report that there’s nothing significant to report or that we just can’t get there from here.

On the up side, at the rate we upgrade our office technology, I could have as few as one more new computer to go before I call it a full career. So, I’ve got that going for me, which is nice.

What Annoys Jeff this Week?

1. Flossing. I have a hate/hate relationship with flossing. I hate doing it and no matter how gentle I try to be or which kind of floss I use, it always ends up with blood.. and occasionally a crown falling off. In the interest of at least trying to comply with the spirit of my dentist’s request to floss regularly, I’ve worked a water pick into the daily routine. At least it’s never pulled a crown off one of my teeth and the bleeding happens far less often… Although Tuesday night the sink took on the appearance of a crime scene, so maybe it’s not an all that much better solution.

2. Computers. I got a new computer this week. Well, not me, exactly. Uncle got a new computer that he’s assigned to me. The jury is still out on whether it will be any better than the broken down old laptop from 2017 that it’s replacing. I suppose if it manages to consistently boot up from a cold start in anything less than two hours, it’s got to be considered progress. Still, that’s a long way off from being a snappy new machine. No matter how new, it’ll be crippled with whatever “basic load” of software our IT boffins think is necessary to protect us from the enemy and ourselves… and it’ll still be a wildly frustrating piece of equipment to use.

3. Limitations. It’s been an awfully long time since I sat in on ECON 101 or 102. They were requirements for a social science major. I did well enough in them, but God knows I’d never consider myself an economist. I’m pretty good at picking up on basic concepts, though, when conversations turn to commodities pricing, interest rates, and the state of S&P 500. If I put in a little effort, I can mostly follow along with the reasons why they rise and fall and even grasp a few of the implications that might follow on. I do, however, realize my limitations. Having an opinion is a fine thing. Sharing it is a perfectly reasonable thing to do. But it’s really a crying shame that more people on the internet don’t seem to have any sense of their own intellectual limits.

What Annoys Jeff this Week?

1. Logging in. When I boot up my work computer in the morning, I have to log in using my access card and PIN. When I log into Outlook, I use my access card and PIN. One Drive? Access card and PIN. Teams. One more time, log in with access card and PIN. Just to start the day I have to log in using the same credentials four to five times depending what opens on startup. I’m sure there’s some important network security reason this is necessary, but it feels dumb and is 100% a daily irritant. 

2. Upgraded masks. For the last two years, I’ve survived plague free by 1) being vaccinated and boosted, 2) generally avoiding people as much as practical and 3) wearing a standard cloth face covering whenever I had to go into a questionable indoor environment. It hasn’t felt like all that big an ask. With the latest variant, word has gone out that it’s advised to switch over to more robust masks – primarily N95 or KN95 style respirators. That’s well and good, but I’ve spent a ridiculous amount of money so far on various upgraded masks and a host of add on extenders, inserts, and other bits to get a better fit. So far, no combination of any of them has given me a mask that doesn’t immediately blow hot air around my nose and cheeks and turning my glasses into a solid wall of fog sitting on the end of my nose. Not falling victim to the Great Plague is important, but if I can’t be both maximally protected and fog-free, I’m going to have to err on the side of being able to see what the hell I’m doing when I need to leave the house.

3. Maryland’s Republican governor has proposed eliminating taxes on retirees as a means to discourage people from spending their working lives here and then immediately decamping for jurisdictions that don’t tax retirement income. For those who will face a potential tax bill from Maryland when they retire, it has to be a consideration. For instance, if you have the longevity to enjoy a 20-year retirement and the state reaches into your pocket to the tune of $4,000 a year, that’s upwards of $80,000 you’re leaving on the table for the convenience of not moving to a more tax friendly state. That’s not the kind of win the Democratic controlled general assembly will want to hand a popular Republican governor. Given Maryland’s historic love of raising taxes on its residents, it’s not the kind of thing they’d want to do if there the governor was a Democrat, either. I’m an unabashed lover of my native state, and I’d love to be able to make a plan to stay here along the shores of the Chesapeake forever, but unless our fearless leaders end up endorsing a plan like this, finances are all too likely to dictate otherwise when the time comes.  

What Annoys Jeff this Week?

1. Systems of systems. Outlook was down most of the day on Wednesday. That was after three days of fighting another “file sharing” system. It’s possible that this week will enter my personal record books as the one in which I spent the most effort to accomplish the least. I’m sure there are good and fine reasons why all out tech seems to be tits up more often than it’s not, but it continues to be one of the top two or three most reliably annoying elements of the job. It’s just one of the many reasons I’m dedicated to being able to walk out the door in thirteen years, five months, and a hand full of days.

2. The week before Christmas. It’s the week before Christmas, or close enough for all practical proposes. It’s certainly less than eight working hours before my long Christmas holiday commences. It’s also been just about the busiest week of work I can remember since the beginning of the Great Plague. Easily 50% of the week’s dumpster fires are entirely self-inflicted because someone just got around to looking at something that should have been handled last week, or because our electronic communication system suck, or for untold other reasons. I shouldn’t say this with so many bosses, former bosses, and other trusted professionals following along, but with seven hours left in my work year, every single one of my fucks has already been allocated. Anyone coming at me between now and 4:00 Friday afternoon expecting much more than a blank stare is going to be sorely disappointed.

3. Prednisone. Thanks to the as-yet unidentified reason my arm had been broken out in a rash for about three weeks, I had a 4-day course of prednisone this week. The (mostly) good news is that the arm has sort of cleared up – it at least looks a lot better than it did a week ago and I’m not longer tempted to satisfy the itch by scratching it with a circular saw. What the four days of prednisone also gave me was an insatiable craving for salt, rampaging blood glucose levels, an even shorter temper than usual, and I’m pretty sure at least one panic attack. I have no idea how people stay on that stuff for weeks or months on end. Next time I’ll just scratch myself bloody and it will still be a less awful experience. 

A $15 Rolex…

There’s one web-based application that is an indispensable part of the job I was nominally doing today. The trouble is, that app went out of service at about noon yesterday and didn’t come back online until an hour before I punched out for the day today. I’m reasonably good, but cramming 12 hours of work into the last hour of a Friday afternoon isn’t going to happen.

As a tiny cog in our wealthy uncle’s great green machine, I’m no stranger to sitting around with my thumb up my ass. Life in the bureaucracy guarantees you’ll spend a not insignificant amount of time in that position.

I have to wonder, though, if we’re really as dependent on networks, and systems, and processes that are apt to create single points of failure repeatedly, why haven’t we come up with a way for these systems to be redundant or develop some method of continuing to get the job done when the computers don’t work. As it sits now, all it means is a 24 hour backlog waiting for someone (read: me) to clear it out on Monday. That’s assuming the great network administrators in the sky really finished whatever voodoo ceremony was necessary to fix things permanently. That doesn’t even begin to account for the inevitable bitching and complaining from echelons higher than reality wondering why everything is taking so long, suspenses were missed, and we’ve given the distinct impression of not having done a damned thing for almost two full days.

Thank God my terminal doesn’t launch the nukes or make sure a reactor gets shut down safely, because from where I’m sitting the whole creaking edifice feels about as reliable as a $15 Rolex.