Crackberry on Ice
Blackberry confesses software bug for email blackout:
Those "easy fix" can quickly turn into a meltdown. Never underestimate the power of a software change to completely bring down a system. I remember my (former) boss making a quick, simple patch for our manufacturing folks (he used to maintain the code but was away from it for some time when he did the fix) but didn't thoroughly test it and guess what? It broke the system so bad, there had to be another fix made while holding up a production in the meanwhile. My coworkers and I had a good chuckle over that one...
Copyright 2007, DannyHSDad, All Rights Reserved.
Ruling out those causes, the company has "determined that the incident was
triggered by the introduction of a new, noncritical system routine that was
designed to provide better optimization of the system's cache." In computing
terms, a cache is a temporary storage area for that allows data to be served up
quickly.
Those "easy fix" can quickly turn into a meltdown. Never underestimate the power of a software change to completely bring down a system. I remember my (former) boss making a quick, simple patch for our manufacturing folks (he used to maintain the code but was away from it for some time when he did the fix) but didn't thoroughly test it and guess what? It broke the system so bad, there had to be another fix made while holding up a production in the meanwhile. My coworkers and I had a good chuckle over that one...
Copyright 2007, DannyHSDad, All Rights Reserved.
Labels: risks, software engineering is hard