- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or register to comment.
Give a man a fish, and he’ll be fed for a day
Teach a man to fish, and he’ll be training orcas to attack shipping vesselsComplain about programming languages instead!
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.
the dunning-bugger effect
“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.
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.
Looks at Undertail and Balatro just being a collection of IF statements…
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.
Nah I just changed from “these game devs” to “these game studios”
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.
Learn to code and you’ll be too busy complaining about your own bugs everyday.
Yes, because you’ll be too busy being infuriated by badly designed user interfaces that you realize could have so easily been better.
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
If you learn to code, you learn that major bugs in releases are horrible and indicative of neglect.
In a professional sense my experience is that they’re more often the result of under-staffing and rigid, fixed release schedules.
And changing priorities and scope.
Yeah, it shouldn’t happen in a release. But, if I had a penny for every time I’ve seen the last minute development that wasn’t tested yet and not even due for the current release squeezed in. I’d literally have a pound, or dollar or whatever else has 100 pennies in.
or whatever else has 100 pennies in
Well it’d be 8 shillings, 4 pence, in pre-decimal British currency.
I sometimes suspect that the push for decimalisation was in part to avoid having to teach computers the old system.
Programming a robust global date-time system and having a transparent conversation between metric and *imperial/traditional" units is just a warm-up to show that you can work with the truly demented currency system. Make sure everything is rounded off to the nearest whole ha’penny.
Afaik it actually was, the UK wanted to move more financial calculations to computers and it was a lot easier to use a decimal currency for that
And sheer pigheaded stubbornness.
Yes. Generally, tons of major bugs in a production release are a sign of the company just not working right in general
Yeah, I learned to code almost 20 years ago in order to mod video games, and learned that many bugs and massive problems in mods and games are caused by coders being either extremely lazy or making extremely dumb decisions.
In general, a ginormous problem with basically all software is technical debt and spaghetti code making things roughly increase in inefficiency and unneccesarry, poorly documented complexity at the same rate as hardware advances in compute power.
Basically nobody ever refactors anything, its just bandaids upon bandaids upon bandaids, because a refactor only makes sense in a 1 or 2 year + timeframe, but basically all corporations only exist in a next quarter timeframe.
This Jack Forge guy is just, just starting to downslope from the peak of the dunning kruger graph of competence vs confidence.
Here’s a copy of that image without the watermarks
Didn’t even see the watermarks.
Thanks!
I unironically need glasses.
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”
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.
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.
You won’t have time after spending all day complaining about bad documentation.
You mean missing documentation?
Or whatever this crap is:
- squeebe(a: Any)
Perform squeebing on a.
- multi_iterate(a: Array)
Multi iterate on a.
- physicsObject.delete_with_header()
Delete physics object with header.
I seem to complain more, actually.
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
It’s a bell curve.
Hahahaha
