23
Bug blindness (danluu.com)
submitted 2 months ago by to c/programming@programming.dev
13 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 2 months ago (1 child)

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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 2 months 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...

  • permalink
  • fedilink
  • source
  • parent