this post was submitted on 08 Apr 2025
156 points (97.6% liked)

Technology

69346 readers
3334 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] BackgrndNoize@lemmy.world 26 points 2 weeks ago (10 children)

It’s a big company problem. Here’s why even obvious bugs like this one slip through the cracks: 

  1. The Tyranny of “Requirements”
    In large organizations, everything revolves around the roadmap. If a bug fix isn’t tied to a specific requirement or feature, it gets labeled as “tech debt” and shoved to the bottom of the backlog. And let’s be honest: “tech debt” is corporate-speak for “we’ll deal with this never.”

  2. The Rotating Door of Ownership
    Over eight years, developers and product managers come and go. The person who originally filed the ticket? Long gone. The person who understood the issue? Moved on to another project. Institutional memory fades, and the ticket becomes a relic of the past. Even if the problem is still very much alive. 

  3. The Myth of “Quick Fixes”
    A 13-line patch might seem trivial, but in a legacy codebase, even small changes can have unintended consequences. Without proper tests or documentation, developers are often hesitant to touch old code. The risk of breaking something far outweighs the reward of fixing a non-critical bug. 

  4. The Invisible ROI
    Let’s be real: improving load times doesn’t directly impact the bottom line. Selling Shark Cards (GTA’s virtual currency) does. Companies optimize for metrics that show up on quarterly earnings calls, not for goodwill or user experience, until it’s too late.

[–] SharkAttak@kbin.melroy.org 12 points 2 weeks ago (2 children)

I recently read that's one of the reasons Windows is so messy and bloated, time goes by and so do devs and managers, so it gets increasingly difficult to know what does what, and why.

[–] trolololol@lemmy.world 2 points 2 weeks ago

And that's the same reason Linux and open source doesn't, because when developers are empowered to do things that impact them, shit happens

load more comments (1 replies)
load more comments (8 replies)