TWDiggs wrote on Jul 8
th, 2011 at 12:22pm:
Madfloyd
Quote:(a hole in our process that we have identified and corrected to avoid for the future).
Someone got fired.
Not necessary, while they should have reacted faster, I can tell you that huge blunders do happen in real world computing.
I'm not going to disclose anything that would get me fired, but when I did an upgrade of a Telco System last year over a weekend ( started friday evening, supposed to end sunday afternoon, 3 people in shifts )... The last guy on the last shift discovered while doing the tests ( after the system was back to live status ) that a specific dataset was totally forgotten in the upgrade, and that a whole lot of companies would have been unable to phone coming monday morning... We ( the 3 guys ) ended up all on site during the sunday to monday night ( to the outrage of the project mangler when he discovered it ) and got the missing dataset extracted from the old system, converted to the right format and inserted into the new system. The Telco Customer was happy, the end customer was happy, we were happy ( having to do it again was something we didn't want to do, that why we all gathered on site to
fix it ), only the project mangler was pissed off, but as we had already told him any time to go fuck with other people and let us do our job, we just told him to fuck off ( yet ) another time.
( Oh, on a side not said project mangler decided that the voluntary layoff plan that came a month after was a bright idea...
On another side note : I don't get along well with project managers, unless they just manage the project and let me deal with the technical side )
None of the technical guys was fired... But we all recognized ( both the Telco and us ) that tests and validation on that specific dataset were missed during the tests.