• Ephera@lemmy.ml
    link
    fedilink
    arrow-up
    7
    ·
    12 hours 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.