False
this post was submitted on 17 Jan 2025
800 points (94.1% liked)
Programmer Humor
32939 readers
498 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
Learn to code and you will never stop complaining.
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.
load more comments
(4 replies)
load more comments
(1 replies)
load more comments
(1 replies)
load more comments
(3 replies)
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
Definitely true, I dread to think about how much tech debt these companies have. 😬
That's what I love so much about open source. Currently have a fork of kiTTY going, working on tracking down a little bug I found in my daily use.
This can also be one of the frustrating parts of open source.
Find something you don't like? Fix it. Will the repo owner approve your pull request? Who knows. Maybe they're a bit absentee. Maybe they view the original behavior as working as designed. Maybe your design doesn't fit their architectural model, so they'll (eventually) heavily refactor your changes and merge them in.
You can always stand up a fork, but keeping those two at feature parity and going in the same general direction can become harder and harder with time.
That's not to say not to try! But it also means reaching out to the repo owners/maintainers before making your first change.
100%, sounds interesting! I'm going to spend some time tomorrow looking at a bug in the jellyfin android TV app related to DTS audio over HDMI.
Rock on! Look at us, contributing to the tools we use
If you only use Free Open Source software, you can!
Unfortunately my bank, government, national health, surgery, local shops, food delivery services, etc. don't open source their code. It'd be nice if they did however.
They wouldn't want you to know it all depends on a Frankensteined chunk of spaghetti'd COBOL that hasn't been updated since a guy they forgot about set it up before he retired in like 1996. And they're just betting that, if they don't look at it too hard, it won't oopsie a cascade of critical failures.
load more comments
(1 replies)
load more comments
(1 replies)
True open source software runs on frustrated developers
But yeah, that is a really nice part of FOSS. I have myself been in situations where I just went and fixed a big myself because it annoyed me lol
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"
load more comments
(3 replies)
Longtime software dev here. I complain about code bugs all the time - I'm like, who the fuck wrote and tested this piece of crap?
The answer is probably you.
10% of the time its me. 90% of the time it's me from the past.
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.
load more comments
(1 replies)
load more comments
(4 replies)
Wrong.
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.
load more comments
(5 replies)
load more comments
(1 replies)
I seem to complain more, actually.
Seriously, every time I see null interpolated in a receipt or email I always think "you fucking donkeys".
load more comments
(3 replies)
load more comments
(1 replies)
True. Now I'm more triggered by the mere existence of some bugs because I can't fucking fathom how they'd even exist in the first place.
That's not true - I'm complaining about the bugs in our software almost every day!
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 😅
load more comments
(2 replies)
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!"
load more comments
(2 replies)
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.
load more comments
(1 replies)
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 ?”
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.
load more comments
(3 replies)
Learn to code and you'll wonder how in the hell some bugs even got created
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.
load more comments
(7 replies)
Yes, because you'll be too busy being infuriated by badly designed user interfaces that you realize could have so easily been better.
You won't have time after spending all day complaining about bad documentation.
load more comments
(2 replies)
No I for sure complain, but for date bugs.. I'll be forgiving
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.
More nuanced reply: I do tend to complain
- less about certain bugs and limitations, where I can understand that the problem is harder than it seems
- and more about others, where I have to imagine a poor intern dragged around by bad advice for several sprints, finally marking the task done (forehead sweating and all), even though they did not really know what they were doing even for a minute.
view more: next ›