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.
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
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.
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.
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.
I'm a baby in the FF fandom, 15 was my first ever FF game, although I do know a decent amount due to my mom being a longtime fan since FF6. I found it funny that the game was advertised as "good for newcomers and old fans" cause all I felt was disappointment about my first ever FF game, while my mom sat there pissed thinking about how she wasted money on a day one edition (that we didn't open till December 2024, lol)
That game.... I wanted to like it, but after hearing about how good the previous FFs are, and just knowing how good other JRPG series are, I can't believe they flopped so hard like that. Good thing is the other games can't be worse, so that's nice.
I genuinely enjoyed the early game. It had a lot of promise, the build up of tension was engaging, the world they laid out was exactly the kind of FF7 techno-magical cyberpunk and sorcery mish mash Final Fantasy does well. I loved the characters as they were introduced and was curious to see whether the wanna-be boy band aesthetic would culminate in an FFX-2 style dance battle motif.
But its obvious they just ran out of gas after the first major arc. All that world building up front, but the game completely falls apart after you leave the main continent. By then of the game, you're literally On Rails after giving you this rich open world to explore for a hundred hours upfront. Tons of buildup but very little payoff. Not what you want in an FF title. I was deeply disappointed in FF13's Big Hallway style of storytelling, but at least the story paid out in the end.
That's not true - I'm complaining about the bugs in our software almost every day!
My favorite part is guessing what they do that results in the bug!
Right?? That's one of my favorite aspects, like there's a weird bug and you can kind of backtrack what happened like "Oh I wasn't supposed to jump out of the car I had to walk through the precise path, I missed the trigger or something I guess??"
Show a man some bugs and he will be miserable for one day.
Teach a man how to code bad and he will be miserable for his whole life.
Tbh, while it is funny out-of-context, I encountered the same exact thing (and I can guaran-fuckin-tee the offender used copilot for this).
It's not funny to be on the receiving end of this, ESPECIALLY in professional environment, where you should not react like that 😅
I agree, but would like to add I find AI generated code without thought or care put into understanding it more offensive than this to begin with.
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
Learn to code and you'll wonder how in the hell some bugs even got created
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.
Learn to code and you will never stop complaining.
I must have learned programming wrong, then, because dear ducking god, the amount of incompetent shit I have to see is surreal.
One system we've got from a different state was marketed as having geolocation. It doesn't. All object relations have to be created manually in a separate page, as in, you register a city, then register an address, THEN, on a different page, you connect the two. Now imagine this for some 24 objects. It has some specific profile permissions hard coded by id (like, only profile with id 4 can create some stuff)
This is just the shit I remember off the top of my head. The cherry on top is that they didn't validate unique emails for users, you could have 999 users with the same email and no way for them to reset their passwords. I asked why: "we didn't think about it"
I asked why: "we didn't think about it"
I have Simon Pegg in Hot Fuzz ringing in my ears: "IT'S YOUR JOB!"
As a software engineer, annoying bugs that should be so simple to fix are so frustrating! I wish I could just have a crack and fixing it myself!
Whenever I feel like this I think back to how many of those "simple" bugs I've had to fix in my own code and how many years it took off my life expectancy and feel a little connection with the poor developer who is probably currently losing their hair over this too
Yes, because you'll be too busy being infuriated by badly designed user interfaces that you realize could have so easily been better.
I start to appreciate games that implement complex and sometimes rarely noticeable (immersive, boo) mechanics that come off naturally. And I notice how a thought pattern behind bad ones could've progressed.
Bugs? My favs are buggy to the point some of these bugs became their own mechanics. I only get annoyed when the game bores me out, and if bugs can't make me feel like it, it's fine. And some better-done games are pretty boring to me.
No it just makes me even more frustrated. The amount of incompetence and neglect I see and have to deal with on a daily basis, even with software developed by multi-million dollar corporations, is astonishing.
Why is modern webdev such a clusterfuck? Why does VisualStudio take multiple seconds to open an empty project? Why does Nvidia's control panel have multiple seconds long pauses to switch between settings categories or loading lists? Why does this game run like garbage on a 4090 when it has mostly static environments and the graphics aren't even that good?
I could go on but I'd be here all day. All of those things, with the exception of webdev (because god there's so much shit in there...), could be easily fixed* or should've never gotten that bad in the first place.
*Provided the entire architecture isn't garbage, otherwise see the rest of the sentence...
And I know much of it is not necessarily the fault of the devs, with management and deadlines preventing them from doing the best possible job, I myself was forced to release half broken updates a few times because of that, but they are not the only problem.
There's a real problem in today's programming culture with thinking that computers are so fast, any garbage code you write will be fast enough, or that you only need to optimize the hot path. Apply that philosophy throughout all your codebase, and suddenly there is no hot path, everything runs like shit. People should also actually learn how things work, not just frameworks, otherwise they won't be able to make informed decisions about what they write.
Also stuff like "Clean Code" and other similarly dogmatic principles still permeate many of the codebases I see. Nigh implementable jungles of <10 lines long functions and OOP garbage that make working with everything a massive pain, other than making every function call virtual and thrashing performance. You need to maintain such a massive amount of context in your head just to figure out the flow of a particular piece of code, with the aid of a debugger because everything is done through abstract classes or interfaces, that even making the smallest change becomes a tedious and error prone task.
Also fuck dynamically typed languages. They suck, every single one of them.
False
Understanding how software is made, and what are best software engineering practices to make stable software only makes hate AAA studios that release overpriced crashy messes even more.
You won't have time after spending all day complaining about bad documentation.
More nuanced reply: I do tend to complain
Instead they'll become curiosities leading down rabbit holes to understand why and how they happened.
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 ?”
Lies
Nah I just changed from "these game devs" to "these game studios"
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.
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.
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 vessels
Now i complain about both the bugs in my games and the bugs in other games
Post funny things about programming here! (Or just rant about your favourite programming language.)
