all 14 comments

sorted by: hot top controversial new old
[–] 54 points 1 year ago* (3 children)

It's a race condition that doesn't get triggered when you run the program through a debugger or with copious amounts of debug log output 💀

  • source
  • hideshow 3 child comments
  • [–] [S] 28 points 1 year ago (3 children)

    Only thing worse is not finding the bug that only happens in release mode

  • source
  • hideshow 3 child comments
  • [–] 7 points 1 year ago* (1 child)

    Try a bug that sporadically happens only in release mode, with no clear connection to anything else, only to find out years later it only happens when someone uses the microwave for too long in the break room.

    "You know, we always get this error after lunch when I reheat leftover soup."

    Goddamnit Kyle!

  • source
  • parent
  • hideshow 1 child comment
  • [–] 21 points 1 year ago (1 child)

    Do trick 33B: Blame it on the crappy corporate anti-virus solution.

    Works always because nobody can say anything against that. Nobody knows exactly how it works, if it's secretly sending your data to the NSA for corporate espionage and if you would disable it, everything would be insecure.

  • source
  • hideshow 1 child comment
  • [–] 8 points 1 year ago

    The firewall always gets new rules somehow.

    Everybody swears the AI feature that adds random rules is disabled, and it has a log that shows the rules don't come from it anyway. Yet, the rules keep appearing.

  • source
  • parent
  • [–] 6 points 1 year ago

    When you test in prod all bugs are release mode.

  • source
  • Undocumented feature flag in a plug-in, that changes the behavior drastically when in any deployment mode.

  • source
  • [–] 2 points 1 year ago

    Fucking R8 (Android optimizer/obfuscator)

  • source
  • [–] 1 point 1 year ago

    This is why you have play testers

  • source