this post was submitted on 20 May 2024
1499 points (97.6% liked)
Programmer Humor
19813 readers
410 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It seems like I'm constantly finding bugs in businesses' apps. Do they not have people test them?
They do, and they have a backlog of hundreds of issues to fix and they must prioritise then. If fixing a bug doesn't make money, it's not priority.
I deal with this every day. It hurts me to my core.
I hate how they'll spend 4 years squashing all the bugs.........and then they cancel the software, and release a new buggy version.
i will never forgive the emby team for creating the single most idiotic (although rather funny) transcoding system.
It has a resolution selection, along with a bitrate selection, so you would think it forces transcoding.
It turns out the resolution is actually just a suggestion, and the bitrate is what it targets, if it doesn't meet the bitrate, it will transcode, and if you get lucky, it might transcode to the specified resolution.
cough Sonos
I am steadfast that I will occasionally take some time and kill off some low hanging fruit. For me, its kind of like a break and lets me clear my head on the bigger issues.
Even then, there are bugs that need multiple people (design, engineering, content, QA, etc) and are not something that can be fixed on a whim.
Those would not be considered low hanging fruit.
The problem is that what users consider low hanging fruit is often not, and what is low hanging fruit for devs, is invisible stuff that users don't notice. The intersection is the tastiest low hanging fruit, but as such it's also rare and easily picked by anyone.
I never said that users were involved in this. This is just grabbing some bugs off the queue that are simple to fix but have been deprioritized by project manager.
But they do make the customer happy because they are the one that submitted the bug.
sure they do, you're one of them
As someone in the dev team for a "business app", we probably know about most or all of them, but they're just not important enough for anyone in management to prioritize them as part of a sprint. It's also possible no one has given us reproducible steps to make them happen, so we just straight up don't know what to fix. Usually the former though.
they test them...
Whether they do anything with that testing is another story,.
We are supposed to be testing them? /s
you already are smh, you just don't know it!
I would fix that bug but the complete rewrite that management has had me working on for the past two years will make it obsolete anyway.
Ah, the circle of life
Sometimes no.
Yes, they're called "customers".
Sometimes. Other times they layoff the QAs and anyone else whose job is about quality.
They usually do yes however it's all about prioritization.
You may have hundreds or thousands or open requests and issues.
With tens of thousands of closed issues that were either not reproducible, not actually problems, or largely indecipherable.
There's usually a feature roadmap which is where most of the development money and time is spent. If it's an older business application then certain bugs might easily take weeks to find, fix, test, validate, go through user acceptance, A/B test, and then deploy. But fixing is expensive work, so if the bug isn't severe it's usually deprioritized next to higher priority work.