chat

in the latter 3 years of my previous job i worked on development of 2 products that ended up being duds, one was canceled right after completion but before it hit the market and the other was released but there's no demand so they stopped further development immediately (which tmk is still the case).

This is always fun when you're working on "wholesale" (strictly in-org) projects, dump a ton of capital hours into something, and then it gets rugpulled right at the end of implementation because it turns out that the middle management ghoul who requested it never actually vetted the new automation process with the finance department stakeholders that it directly affects, and it turns out that the "automation" actually dumps a fuckton more manual work on them. And there are no consequences because the aforementioned middle management ghoul just retires a few months later anyway, after the poor sap who had to do all the development work -- and requirements re-analysis because the project "docs" were screenshots of XML pasted in a multi-tab Excel sheet -- missed like four holidays in a row AND I WILL NEVER GET THAT TIME BACK YOU SONS OF BITCHES

Every fucking year they pull this shit. I get handed some massive project near the beginning of the year, and then I keep getting pulled off of it in order to do random break-fix work on other shit that keeps breaking because we have no QA, no standards, no accountability, not even code reviews, and then October rolls around and it is suddenly the massive project from Q1 is The Most Important Thing Ever because the capital work order funding goes bye-bye on December 31st, so now it's motherfucking crunch time baybee, and guess who's the Cap'n.

Between the 60+ hour weeks and the RTO chumpfuckery, I'm barely keeping it together.