The Joys (And “Joys”) Of Being Good At My Job

All of last week’s chickens have come home to roost. The letter I sent got responses, the work I was doing has come around back to me, and all of my crafting in Final Fantasy 14 has culminated in my plans for tonight. I’ll write more about how all that goes later this week, I’m sure, but suffice it to say that I’ve been very productive and, after lots of effort, I’m finally ready to actually make the gear itself. I’m also going to hold off on writing more about my letter responses and my subsequent therapy session for a bit longer, until I’ve had the time to process it all a little while longer. Instead, today I’m going to talk about the absolute nightmare that is this one bug I found at work. Thankfully, I found it and, since it’s my job to do that, things are going well for me in terms of my career. This will not pose any problems for me in that direction and will more likely be a feather in my cap than a hindrance since I found a horrible problem in an unorthodox way that would surely have eventually happened in the field but might otherwise have never occured in a testing environment. It’s just going to be a lot of work for me and I can’t even take satisfaction in foreseeing a thorny issue since I just sort of bumbled into this. I mean, I absolutely made the decisions that resulted in me learning that it’s possible to burn out an essential component of this product in a way that is safe but only because it renders the entire thing unuseable, but I didn’t think it was going to go poorly. I was actually looking for something unrelated that I still haven’t pinned down, but such is the life of a tester. You do a lot of inexplicable or unlikely things and stumble into bugs you never could have anticipated.

Continue reading