Worst Software Bugs in History

personal, code 0 comments suggest edit

Wired News has a very interesting article on History’s worst software flaws.

It makes me think of my worst software bug when I first started off as an ASP developer right out of college. I was working on a large music community website and was told to implement a “Forgot Password” feature. Sounds easy enough. I coded it, ran a quick test, and then deployed it (that alone should rankle your feathers).

We didn’t quite have a formal deployment process at the time. A few days later, we find out that the code never sent out any emails, and never logged who made the requests, leaving us no way to really know how many users were affected.

I believe we found out (and my memory is hazy here), through a relative of our client’s president. After reviewing the code, there was no way it could have sent out emails. There was a glaring bug in there, which makes me wonder how it passed my test.

In any case, I coded on egg shells for a while after that, fearing I might lose my first coding job.

Found a typo or error? Suggest an edit! If accepted, your contribution is listed automatically here.



4 responses

  1. Avatar for Scott Williams
    Scott Williams November 8th, 2005

    I think my first bug was when I quickly "fixed" an update query in an application and forgot to include a WHERE clause. Fortunately the table was recently backed up and we only lost a couple of rows.

  2. Avatar for jayson knight
    jayson knight November 9th, 2005

    Haha Scott...I've done that before. Thank god for understanding DBA's :-).

  3. Avatar for Bogdan Costea
    Bogdan Costea July 25th, 2008

    I lost about half a million rows by running test code in production by mistake, everybody does this at least once.
    Thank god for "select as of timestamp"!

  4. Avatar for Jesus DeLaTorre
    Jesus DeLaTorre July 28th, 2008

    I've done the update statment with no where clause
    Except we didn't have a backup. Thank god it was for a nonprofit website.