- cross-posted to:
- programmer_humor@programming.dev
- cross-posted to:
- programmer_humor@programming.dev
You must log in or register to comment.
At minimum I think it would stop people from calling devs lazy. I don’t code, but even I know for how boring Ubisoft games are, none of them were “lazy” outputs.
Complain about programming languages instead!
I can code pretty well. I’m a qa tester. Complaining about videogames is my mostprechious pasttime
learn to code and you’ll forever more be going “i could probably fix this if i could be fucked to get familiar with the codebase”
Staring at some open source code in horror, like you just flipped to a random page of the Necronomicon.
False
Wrong.
ITT: Learn to code and you’ll never understand irony again!
Yeah, that’s something a shitty developer who is bad at debug would say.
Bugs frustrate me more because I can often guess at why they are happening and how to fix them but can’t just apply the fix myself. Even more frustrating when there’s an update and I’ll think, “oooh maybe they finally fixed that annoying bug!” and then see it again shortly after installing the update.
“ugh I know exactly why this is happening” is such a frustrating feeling. Especially when it’s stuff that should’ve been found in testing, or that you know probably was found in testing, but they deprioritized the fix.
the dunning-bugger effect
Sometimes what’s worse is when I am pretty sure something they suggest won’t fix the bug and then it does fix it. Like I experienced a race condition in my Android email app and talked to support about it. They said try clear app data / cache and see if it worked. I thought there is no way that would solve it and they’re just giving be the boilerplate support thing. It did fix it.
Now I’m even more scared at what their code is doing.
The DMR in call of duty years ago. “Here’s a bug with a gun that instakills from 4 miles away that breaks the game dynamics. It’s literally unplayable. Instead we added more features that make us money.”
Bugs frustrate me more because I can often guess at why they are happening and how to fix them but can’t just apply the fix myself.
That’s like a big portion of bugs lmao, lots of bugs exist because the spaghettification of the code makes it too costly to fix. Do you really think devs don’t know why the bugs are there? They usually can’t be fixed because there is no time or no willingness from management or the root cause is so deeply rooted it requires a shit ton of work to be able to fix it at all.
Yeah that’s fair, though it doesn’t help with the frustration. Especially when it’s management getting in the way of things. Like with all the enshitification, my guess is that there’s a dev or team of devs that hate themselves for going along with it.
I seem to complain more, actually.
It’s a bell curve.
Seriously, every time I see null interpolated in a receipt or email I always think “you fucking donkeys”.
Dear {{ user.first_name }}, We would like to personally thank you for registering at {{ brand.name }}! Regards, {{ employee.name }}Like, it printing out “Null”?
Yeah
Not true, I bitch about them more than ever
“Who fast-tracked this shit?” -me
“It’s a small change, should be safe, we will test it in production” -also me
I am still complaining, but now I blame the managers
“wow, what director level ass pushed them so hard that they had to leave that bug in?”
I think of the T-pose all the time in cyberpunk, that was a bug that was horrible but obviously it was tracked somewhere, and some director was like “it’s fine, ship it”
There was a Dead or Alive game in which a manager literally released it before it was ready without consulting with the team. The game was still in beta and a glitchy mess.
The PS2 version of DoA2? I vaguely recall reading about it, also how the Dreamcast version turned out to be the complete one.
Still stuck on FF15. So much time and energy invested in reinventing Unreal Engine… badly. Then they have to attack the corners of the actual story with a hacksaw to push a title seven years in development out the door half baked.
Knowing how to code and interacting with stuff like the nintendo e shop scrollimg performance being super shit makes me think I would absolutely be fired if I deployed shit like that in prod for millions of users.
Now i complain about both the bugs in my games and the bugs in other games
I still complain about bugs, but instead of blaming devs or qa I blame managerial positions and stakeholders.
Huge bug in game exists:
Non dev gamers: “How didn’t they catch this blatant issue?”
Dev gamers: “How many times the issue was addressed just to be told to work on something else with greater priority like <random stupid thing>?”
Nah, I complain more about things. Especially ones that should work. “Oh you didn’t test this in my preferred browser and now it only works in Chrome, idiot”. I can see the error and I know why the shortcut was taken or the test that would have caught it was skipped and it pisses me off.
Sometimes it’s deadlines and outside forces and not laziness, and for those the coder is forgiven. And sometimes the bug is hilarious and not frustrating. But if you have an e-commerce site, basic utility, healthcare portal, or other required site that is broken because you couldn’t be arsed to test with something other chrome on a desktop monitor then fuck right off.
One of the things that pissed me off fierce was when my natural gas utility company redid their website, and got redirected to a landing page with an autoplaying video. Excuse me I’m already a customer, I want to spend twenty seconds paying my bill, not two minutes dealing with unnecessary crap someone thinks looks better or more trendy.
As someone who had a career as a web developer and had to build sites that worked pixel perfect on multiple devices and clients I think game developers are jokers
Nah I just changed from “these game devs” to “these game studios”
