The Rot That Is “AI” Keeps Spreading Into Things I Love

Square Enix, the company that publishes (and makes, for the most part, but it’s also a little more complicated than that because of how companies are structured) Final Fantasy 14, has announced recently that they’re partnering with a bunch of local academics in Japan to study current “AI” products in an effort to have seventy percent of all Quality Assurance (testing, aka the work I do) and debugging fully automated sometime during 2027. Now, this is, of course, patently ridiculous and not something that will actually work out or is even possible in the way they want it to work, but the past years of watching the tech industry get gutted and people begin to lose their jobs to “AI” bullshit has taught me the obvious lesson that it doesn’t need to work for it to be adopted. It doesn’t need to be good for people to lose their jobs. It just needs to be good enough that someone can pretend it’s great and fire all of their QA staff in order to “reduce costs” so that shareholders can get a fraction of a decimal percent more money at the end of the fiscal year. It’s bleak, I know, but all of the studies done on it, every post-mortem on “AI Workflows” and almost every single company to adopt it have all shown that it is a neutral move at BEST and a net loss in every other case. People hate needing to check over the work of “AI” because of how often its wrong. People hate being forced to use tools that don’t work properly. As I watch it chip away at the industry I work in and watch it start being focused specifically on the work I do, I can’t help but feel like I’m staring down the barrel of a loaded gun every time it comes up. Which means that, every time someone jokes about it trying to take my job, I feel like they’re joking about the gun pointed at me going off and then insisting that it will never actually happen whenever I try to talk about how all this feels or why it’s bad to have around.

Continue reading

“Process” Doesn’t Have To Be A Dirty Word

Once again, at potentially the worst possible time for my team, we are being forced to adopt a new company-wide process. My boss is encouraging everyone to participate early and get involved, that way we can provide feedback that will hopefully push this new process in a direction that will work better for everyone involved, but I could see the exhaustion and loss of morale on my coworkers’ faces as what was supposed to be a quick aside turned into an hour-long discussion. To be entirely fair to my coworkers, the only reason I wasn’t having a bad time is because it didn’t impact me and I’m already a heavy user of the tool being forced to fit everyone else. You see, the tool in question is a software development and bug tracking product with a well-built database and plenty of customizability, one that the software developers and testers have been using for over half a decade, to the degree that we barely think about it anymore (I’m not going to name names or get more specific than this for reasons of plausible deniability and keeping my writing away from my work life). What sucks for me specifically, though, is that there is rumor going around that all of the people who HAVE been using the tool in a way that works really well for us are going to be forced to use it this other way, that everyone else is using it, just so everyone uses the tool the same way.

Continue reading