Subtext And Performative Extroversion Are The Key To A Good Work Schedule

On top of everything going on, all the woes of society and my on-going issues with finding a decent antidepressant that works for me, things at my job are picking back up again. Our project has been announced, we’ve gotten through all the manufacturing hurdles, and it is officially released to production as of a couple weeks ago. Which means that development can finally resume. That’s right. It’s released and actively being sold, but we’re back to working on it again. This isn’t terribly unusual for a lot of products (especially on stuff with lead-times as large as ours are–multiple months). A lot of things will be announced, get demonstrated or marketed, and have their designs shipped to factories to be produced long before development will stop working on them. Some of that work is, of course, designing future versions of the product, making improvements, and incorporating feedback based on customer experiences. A lot of it, though, is just the same work that’s been done the whole time but now focused solely on trying to remove as much material from the project as possible in order to bring down the cost of producing it. Sometimes that means chasing down ideas developers and engineers had but didn’t have a chance to try out during the initial development phase. Sometimes that’s just making choices to combat newly discovered problems that only came up after the product existed and was being used long enough. Regardless of the specifics, I’m now entering into what is going to be the longest period of heavy physical labor on this project, albeit at a much different pace than I was doing it earlier this year.

Continue reading

I’d Rather Let My Coworkers Waste Our Time Than Bail Us Out Of A Horrible Meeting

I had a testers meeting last week. It was a bit impromtu, but such meetings usually are. My little team of testers is only three people these days, and while we do have an obvious senior tester who should be in charge, he’s not really the commanding sort. The next most senior tester, who has a few years in the job at the company on me (but I might have more total years testing thanks to my job before this one) and is the same “rank” as me tends to be the one to call the meetings. Usually because he’s got a lot of work coming up and knows he’ll need some help from someone else because our lab assistant (who usually helps him) won’t be available or because it takes a degree of expertise the lab assistant lacks. It helps him to sit down and talk through all this stuff when he needs more than just one-off help, which is why he calls most of these meetings. My other coworker and I just call on each other as needed and talk through that kind of stuff on a day-to-day basis, but we share a great deal of expertise and can ask each other to do things without worrying about how well it’ll get done. Which, unfortunately, is not something we can expect from this other guy since he has done his best to avoid learning anything about the deeper aspects of our testing over the years whereas all three of us are fairly proficient in most of his testing. Beyond that, we also have status update meetings from time to time, just to get together and talk about what’s going on and what’s coming up, but we haven’t done any of those meetings in a while because it has been pretty much the same stuff going on for over a year at this point.

Continue reading

Putting My Annoyingly Competitive Coworkers To Work

Last week, I wrote about how I was feeling better and how I was kind of excited about being able to actually put in some effort at work without feeling awful for a week or more. I wound up setting a personal record for testing cycles performed entirely on accident. I’d forgotten that my previous record was counted using only half of what I’m now calling a cycle (since I was testing something else then), so I’d only done thirty cycles in a single day back when I was still feeling fairly hale despite all the pain I was in last summer and on Friday I wound up doing thirty-seven (specifically to smooth out the total count to a nice round number). I paid for it all weekend, of course, but I was feeling mostly better by Sunday and back to about ninety percent by the time I hauled myself into work yesterday morning (or, well, a week ago yesterday as you’re reading this). I felt well enough to log another thirty cycles, even, and woke up today feeling mostly alright. My hands are in the worst shape, between the blisters, the muscle tightness, and the lingering tenderness from my burns almost three weeks ago, but even so I’m able to keep up the work and wound up logging an impressive fifty cycles. The problem is, while I’m making great progress on this testing, it will take me weeks to get to the total number I need to call this test finished. After all, even if I can keep up doing fifty a day–or even get it up to my target of one hundred–that’s still ten to twenty days of work to get to one thousand (the number we’ve picked for this test). I need it to happen faster than that and I’d really prefer to not be exhausting myself every day given how much OTHER work I still need to do before this project is finished.

Continue reading

Coping With The Specter Of Human Fragility

I mentioned in last week’s “welcome” post about the stress I was dealing with as I was forced to confront the fact that the products I work on and test are zero steps removed from the potential to cause significant structural damage, debilitating injury, or even death if things go wrong enough or are used deliberately incorrectly. It was all for a presentation that didn’t REALLY go the way I’d hoped it would–either completely silent as everyone grappled with the fact that the Specter of Human Fragility loomed large over all the work I do or vocal recognition of the same–but I have also been thinking about it pretty much ever since. Not constantly, mind you. I’d be pulling my hair out if I was constantly thinking about it. I can put the thoughts away for a time now that the presentation is over and I don’t have my usual anxiety constantly bringing it to the front of my mind. Which has made me wonder why the presentation made me anxious enough to think about the potential for harm inherent in my work while the potential for harm inherent in my work doesn’t seem to register nearly as much. I’ve also been polling my coworkers about how they think about it, if they think about it all, and how they handle the thought all the while. Most of them seem to handle it much like I do (just not thinking about it/working to ignore it) and the few deviations aren’t particularly remarkable in their deviation. None of us are immune to the thought. None of us are uncaring. We all live with it in our minds as we each work through our parts in making sure something horrible never happens, but it doesn’t seem to weigh on any of us particularly heavily.

Continue reading

The Slow, Grinding Burnout Of Constantly Finding Problems

One day deeper into the week, one more day of fruitless work on a project I can’t talk about behind me. I’m not as upset about everything as I was yesterday, though I’m still a little upset and frustrated, but now I’m feeling extra worn down because we’re still unable to figure out why things aren’t working the way we want them to and how nothing we do that improves those results makes any kind of sense. It has everyone stumped and while we have been able to make slowly improving progress over the past two months, we haven’t really fixed things yet. It is exhausting to work on, mentally and emotionally, because we’re just beating out heads against a problem, and it is exhausting physically because any proposals about different methodology or improvements require a decent amount of heavy labor from me. This work has become every kind of exhausting and I can feel myself less and less able to spring back from it with every passing day. Sure, nothing I’m doing is wrong or a failure or anything like that, but it sure feels like a failure when I’ve been working on a problem this long and this consistently but haven’t been able to figure anything out. Sure, my job is to collect data and tell people that things are wrong, but I clearly understand the problems and how they play out better than everyone else (as my repeated explanations prove almost daily) so it feels like some part of the solution is my responsibility. Regardless of whether that is right or wrong, it is how I feel and these repeated days of zero progress despite my efforts have me feeling incredibly drained.

Continue reading

Venting What Steam I Can From Work Frustrations

Today has been shitty and exhausting. Not the usual kind of shitty where it’s mostly my depression, my despair at the world in general, or me needlessly spiraling over some unlikely anxiety, nor is i shitty in the sudden-crisis-at-work kind of way. No, today, I got to spend four hours doing manual labor I can’t talk to anyone about to test a project I can’t talk about in any level of specificity while being watched by a bunch of people who frequently ignored my advice and all but shouted me down when I suggested that something they were worried about wasn’t actually a problem based on the hundreds of hours of experience I’ve gotten with the product at the heart of this project. I had to spend ten minutes enduring their nattering and catastrophizing about how what they observed could be the source of all these problems we’ve been trying to solve for months now before I could prove myself correct (that it was an optical illusion caused by their point of view and multi-directional movement of the thing I was moving around). I wasn’t going to let them interrupt my data collection to do the unnecessary thing they wanted to do, since that would require dismantling the current test, doing an entirely different test, setting my current test back up again, and then calibrating the measuring tools again. It took me all of a minute to prove they were wrong when I finally set their test up in a much faster and easier way than they thought it had to be done. As I moved to continue testing following their reluctant agreement that I was correct, one of them said “and now we’re never going to hear the end of it.” That really soured my mood, which is worth remarking since I wasn’t in a great mood already based on the whole “hours of manual labor while those coworkers stood around and wrote down numbers or pressed buttons” thing.

Continue reading

My Entire Career Contained Within An Hour Of Me Being Unfortunately Correct

One of the most frustrating experiences I have far too often at work is that I am ultimately proven right about something. It happens often enough that I stopped keeping track, but apparently not often enough that anyone remembers how frequently it happens. That or they’re just ignoring it because I haven’t gone and rubbed anyone’s nose in it. As much as you might think otherwise, given my propensity for predicting bad outcomes and the frequency with which my warnings are proven out, I don’t enjoy telling people that I told them so. There is little joy in those moments for me since I don’t particularly appreciate seeing other people struggle or suffer, and I get little satisfaction from having been correct that something bad would happen when that bad thing has happened. Usually, there’s lots of work to do and my life has suddenly become more difficult as I either have to lend a hand to clean up whatever mess (literal or metaphorical) has been made or have to find a way to still do my work in what has become a shortened timeline. I don’t have the time to bask in being right and everyone is usually better served if I don’t point out how wrong they were, how right I was, and how they should listen to me in the future. People’s feelings get hurt by things like that and it usually makes people less likely to listen in the future, not more likely. That said, I’m beginning to wonder if maybe I should be making a point of it more often than I do.

Continue reading

The Drudgery Of My Job Is A Metaphor For My Life

Yesterday (well, yesterday from the day I wrote this a bit over a week and a half ago because of holiday blog displacement and me trying to bank some writing before I’m hosting people), I spent two hours turning a hefty box full of various electrical components on and off. My calculations tell me that I did it approximately eight hundred times in those two hours, using a total of four different combinations of powering up and down steps. I was trying to get it to burn out since we’ve been getting reports of issues in the field with this particular box of electronics burning itself out when users are turning it on in the morning. While this did not make a lot of sense to us, given how hard we hit these things in the lab during the course of developing them and then testing them, we figured it was worth looking into. By which I mean the engineers and my manager figured it was worth looking into and the other testers figured it was worth me testing because, now that my urgent project is done, I don’t have anything that needs to be done yesterday while all the other testers are still working on that schedule.

Continue reading

I Fell Into A Burnout String That’s Dire

I am writing this on the sixth day of November and I am already so incredibly burned out that I’m considering taking time away from work already. Well, not “already” since I haven’t had much time away from work in about a year that wasn’t set aside for a specific purpose. The holidays last winter, visiting a friend/interviewing for a job that I didn’t get, going to Spain, my friends’ wedding, my move, and then labor day weekend (which wound up being preparations for my grandmother’s passing)… All the time I’ve taken away from work has been specifically for an event of some kind or to deal with some kind of major life stress. I haven’t had a proper do-nothing, restful vacation since Thanksgiving of 2022 and that barely counts since I was preparing myself for family therapy with my sister and parents. The last time I took a vacation and didn’t have something horrible, stressful, or upsetting happen immediately afterwards was when I went to a cabin with my friends and siblings for most of a week in the summer of 2022. Which only counts because the stressful thing that happened after that was something I’d mostly gotten used to dealing with (my eye problems flaring up). I really need a proper rest and I really hope I can get one this Thanksgiving. Next week, as you’re reading this.

Continue reading

Work/Life Balance Means Spending 12 Hours At Work, Right?

As I mentioned in Tuesday’s post, work has been staggeringly busy. I haven’t even had time to think about my organization project this past week since every single day has been over eleven hours of constant effort and focus. Well, not every day. I had one short day, since my friends where getting married and I wouldn’t miss that for anything, but that was the day that turned my “one long day to make up for one short day” plan for this week into my “every day is a long day since there’s so much that needs doing now, if not sooner” reality. Turns out something we thought wasn’t working for one specific reason actually wasn’t working for an unknown reason, which we know because I proved that the specific reason wasn’t actually at fault. Turns out the assumptions I’ve based my last three months of work on were incorrect, actually. Turns out everything we’ve been doing to “fix” the problem actually only hid it. And, as it turns out, the problem is likely more wide-spread than we thought it was but an incidental quirk of the hardware involved might have hidden it in most cases. As of yet, we still don’t know for certain what the cause is. I have some strong suspicions and a theory I’ve been able to back up a bit, but there are still problems with that theory that I haven’t figured out yet. I will continue to work on this problem all day, every day (well, I don’t expect to come in on the weekends, so hopefully only every work day) until we’ve figured it out and then, finally, we can lay this thing to rest.

Continue reading