24
Bug blindness (danluu.com)
you are viewing a single comment's thread
view the rest of the comments
[-] Ephera@lemmy.ml 10 points 1 day ago

I feel like many bugs in the wild just come from business processes slowing everything down, especially in larger companies. It might seem like a bug that can be fixed in half an hour, if anyone spotted it, but instead:

  1. they need to file a ticket
  2. it gets discussed in planning, but postponed because there's an extremely importantâ„¢ deadline (repeat this step like 5 times)
  3. someone from upper management notices the problem and sends an angry mail; it is finally included into the sprint
  4. they implement the change
  5. it gets rejected in code review due to some nitpick
  6. they fix that nitpick
  7. it passes code review and is merged onto main
  8. it gets discussed again in sprint review
  9. it gets shipped two months later
  10. ah crap, something broke; need to bisect a few hundred commits to find out it was this change that broke it
  11. spend half a day preparing and testing a hotfix release, because the next proper release is months away
  12. it gets rejected in code review due to some nitpick
  13. ...you get the idea.

You go through that slew of bullshit exactly once before you learn to turn a blind eye to anything that looks easy to fix.

[-] Valmond@lemmy.dbzer0.com 3 points 3 hours ago

So Ephera, why is this bugfix taking more than 1 hour?!!

Bugs are not possible to evaluate (except the most simple ones) and if you can't completely fix the bug and its deoendency bugs in the original time allocated then everyone will think you just wasted time. Or so it has been for me on those "Agile" jobs.

[-] Ephera@lemmy.ml 1 points 19 minutes ago

Yeah, I didn't even include technical debt into my list, but it comes up so often as well. Chances are someone else already saw the problem, considered fixing it, then saw the mountain of technical debt blocking a fix, and decided to ignore the problem in the end.

For me, thankfully, folks have been understanding so far, when a bug fix takes significantly longer than expected.
But we also explicitly don't estimate bug fixes upfront, because of what you say. You have to diagnose the bug to figure out what solution is required. And the solution can range from a one-line-change to a refactoring of half the codebase. Good luck estimating that...

this post was submitted on 30 Aug 2026
24 points (96.2% liked)

Programming

28304 readers
439 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 3 years ago
MODERATORS