all 8 comments

sorted by: hot top controversial new old
[–] 1 point 3 years ago

The fact that they mention using EMACS makes it even funnier

  • source
  • [–] 1 point 3 years ago (2 children)

    Reminds me when I was working with a guy and he named a database table recieved . I had adapted my code to that, and then one day without warning he renamed it to received - and it took us an hour to figure out why everything broke.

  • source
  • hideshow 4 child comments
  • [–] 0 points 3 years ago (1 child)

    had a co-worker once who called the variable holding the first record in a complicated workflow "rec1st" and the last record "reclst", unaware that in every font used by every code editor except his, a lowercase l and number 1 look identical.

    i spent a day debugging that after he quit.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 3 years ago

    Excel wrongly assuming the year 1900 was a leap year for their timestamps is my favorite bug that will never be fixed because everyone has built workarounds for this already

  • source
  • [–] 0 points 3 years ago (1 child)

    I wrote code for industrial automation years ago (think assembly line machines). I was reviewing production code and found a stupid bug and fixed it, then reinstalled. The motors moved incorrectly - I don't recall if that was the time it smashed glass everywhere, but "fixing" the code definitely broke the program. I could not figure out why...but due to time constraints I sadly had reinsert the bug to put the machine back in production.

    Some nights that still bothers me.

  • source
  • hideshow 2 child comments