- cross-posted to:
- programmer_humor@programming.dev
- cross-posted to:
- programmer_humor@programming.dev
You must log in or register to comment.
I am still complaining, but now I blame the managers
Wrong.
ITT: Learn to code and you’ll never understand irony again!
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
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.
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.
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.
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.
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??”
False
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.
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.True words by a wise programmer
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…
Why is modern webdev such a clusterfuck?
Not a webdev.
Have tried multiple times to “finally figure out how this web stuff works because I’d like a nice website that isn’t a huge chonky slowpoke WordPress install with ad-infested plugins.”
I can’t do it. Gamedev is hard, but makes 1000x more sense than whatever cargo-cult bubblegum-and-hope the modern web runs on.
I probably should learn JS, but I’m very hesitant to even bother with it because it feels like an insane time commitment. Like getting a doctorate from scratch in something you’re not SUPER jazzed about or starting OnePiece from Ep 1.
“Oh cool, you learned that thing everyone complains about! But you know nothing until you get good at ~30 out of 400 different highly opinionated frameworks.”
The input to result ratio just doesn’t seem like it’s there. O.o Maybe I’m just a noob but this is my experience lol.
And don’t even get me started on RAM-munchy Electron apps.
“Why yes, I WOULD love a separate instance of Chrome running for every
messengerapp I use! And I love when Discord is the only support resource! :D”–Nob’dy Ev’r, 2025 A.D
Have fun with JS, everyones most consistent and beloved language.
My favorite part is empty array truthiness. [] is falsy ( [] == true returns false ), but ![] is false. !![] is obviously true. (! is inversion as in all normal languages)
I seem to complain more, actually.
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.
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.
Learn to code and you will never stop complaining.
