8

Worst: Realizing there were crippling and horrible bugs in software that got shipped to customers. Also realizing that we truly don't know the amount of technical debt that contributed to these bugs. My most terrifying comment from a colleague: That software was written on a weekend and the dev was getting 3 hours a sleep a night. One of the bugs I found I was fighting for almost a year to even find what was causing the bug.

Best: Finding those bugs and eradicating them. Having confidence that the bugs we know about are truly dead and gone. Til we meet again...next...

Comments
  • 4
    When you could eliminate a hundred bugs just by refactoring the shit into something readable.

    But don't worry: When you finally do the refactoring, you will see a lot more of the highlevel design bugs, that are currently hidden by the other bugs in front of them...
  • 2
    @Oktokolo Refactoring that code is always on my mind. However, I have been told some things: "don't make a career out of <the software>", and "that software doesn't net us profit". So the persistence of my software nemesis continues.

    Part of the reason for the long time to figure out certain bugs has to do with being put on more profitable projects.
  • 3
    @Demolishun
    Well, if it is used, it might make negative profit due to the bugs frightening users.

    And it honestly is a lot like renting out hotel rooms with cockroaches in them. Sure, they can be well-hidden and all.
    But if you get to know about them, you definitely have to do something about them.
    And refactoring might very well be cheaper than patching em one by one as they are found by customers...
Add Comment