PM needs experiments running this weekend. One set has a NullPointerException. Just told him to tell me when he's fixed it. He's been painful to work with, that at this point I have no empathy. Just cackling as it's not my problem until Monday! 😂

Sometimes I feel like my PM might as well just say "I don't believe in refactoring, as I don't make any mistakes."

When people think you're addicted to gaming, but you're just really keen on developing that next feature. People just don't understand the underappreciated life of an add-on developer. We're shit on by the game developer, and users alike.

When the roast is greater than the rant 😂

Thursday: Realise the data you generated yesterday was useless.
Friday: Accidentally delete all of Thursday's work.
Saturday: Give up and contemplate ones existence...

This is my level of discomfort when seeing the horrible git etiquette of my PM.

Having to use home PC because your office PC takes a millennia to train a classifier. Why not just work from home?

PM: Zip up the prototype and push it to a temporary folder on the master git repo.
Me: *twitch*

E-mail the supervisor saying I'm prioritising this new feature because it's more important. Not because it's currently broke and I'm stuck.

Shows perfect results.
PM: Nice, integrate that into the latest version.
Shows bad results.
PM: Your integration must be wrong.
Show him the file diff, no difference in my implementation.

It's funny how the exact same feature goes to shit immediately after they push all these untested changes.