As the kids say, "it ain't that deep bro." Before, we got paid well to do what we loved, and we were sought out for our ability to code. Now, the "fun" has be

As the kids say, "it ain't that deep bro." Before, we got paid well to do what we loved, and we were sought out for our ability to code. Now, the "fun" has been automated...by our own hands. Seeing the thing that was so highly-prized be minimized and ground into dust is fucking depressing. Well, that and the massive layoffs from "efficiencies" brought about by AI. And the compensation "rationalizations" that come from an employers' market with no end in sight. And the ABSOLUTELY LEGENDARY amounts of cope, especially on this forum. "It was never about the code," they say, as they write the equivalent of a TRD [^0] into a slot machine and pull the lever, hoping to get their hit of efficiency for the hour. So, yeah, I get the BA dude in the article who lights up when they pull out the piece they're knitting. The end is coming for us; might as well take up knitting while waiting for the fall. [^0] https://www.timelytext.com/technical-requirements-document/ https://www.timelytext.com/technical-requirements-document/. I did a stint as a BA in college for a pharma company and converted FRDs into these all of the time. You had to be technical enough to translate business-speak into nerd-speak, but not necessarily technical enough to actually implement these solutions. As a result, we never saw a line of code, since these were handed off to some PM who, I'm assuming, turned these into tickets in whatever their ticketing system was. This was during the waterfall days, so it was probably something god-awful. Writing these was soul-sucking to the maximum degree. How people get satisfaction from this process befuddles me. Maybe it's the real-time back-and-forth arguing that's fun? I'll never know.