Out of all the bugs, the most annoying are the ones that come out and make me say "WTF?!?!? WHY THE FUCK HAS IT BEEN WORKING FOR THE LAST 2 YEARS??!!?!!??? THERE"S NO WAY IT COULD HAVE!"

When the bug surfaces, you investigate and see that it indeed IS a bug and there's no way it would ever work w/o a fix. But then SOMEHOW it's been working just fine for years....

It's like server elves went on strike and said "no more, it's enough covering that bug - it's time you fix it, lazy-ass idiot!"

  • 4
    Happened a lot on 3DEXPERIENCE Platform. Monkey patch after monkey patch methodology!
  • 2
  • 1
    Nuff said
  • 2
    i've had a great time missreading "bugs" for "drugs 😄
  • 1
    cache. it's always the cache
  • 1
    Did a library or platform change? Something get removed from an interface?
  • 2
    @Demolishun neither. There's a non-null constraint on a column. And I forgot to set the value. That part of code has been running fine for years. DB restarts several times a week. No major db changes [apart from ebabled query logging AFTER I started getting sql exc]...
  • 2
    The conclusion I usually come to in that case is that nobody has been using the feature and therefore nobody has noticed. Either that or they (users) noticed but didn’t care
  • 2
    @black-kite Makes sense.

    Except that the failing feature is... login :)
  • 1
    @netikras ha ha ok. Maybe an environment related bug?
  • 0
    Recently bumped into code that took a map, destructured into keys and values sets and put them in a database as 2 lists. Luckily the map was a linked hashmap so the sets order were preserved, but otherwise it would result in pretty horrific bug 🤷‍♂️
Add Comment