The worst software bugs in history

“Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debugging Monday's code.” --Dan Salomon

Anyone who has ever worked in IT knows the pain of debugging, and is probably nodding in agreement to that quote. Debugging is often more time consuming than writing the code itself. Yet, even after all the time spent looking for and removing bugs, a few manage to slip by.

Usually, a bad software bug might result in irritated customers. But, as I learned from this article in Computerworld listing 11 of the worst software bugs in history, sometimes a software bug can be the difference between life and death. Let’s hope your bugs are never this bad.

Want to know the secret to bug-free code? Here it is: Write perfect code all the time. All joking aside, it’s not impossible. In fact, it’s one reason we designed m-Power to use a model-based development approach. The model-based approach means all the applications generated by m-Power have already been thoroughly tested. That means no more debugging! That means more time building apps and less time fixing problems. Who doesn’t want that?

If you want to test m-Power out for yourself, check out our free Test Drive.