Tweet
To cut a long story short....
In September we moved all our work from system A (because it was a pile of crap and riddled with faults) to system B. At the migration date, we saved a complete snapshot of system A's databases and reports in a "Business Objects" universe to act as an archive, so that when we identified problems in system B we could see what was the cause under system A, and fix it. Simple, right?
There were just two problems. Firstly, the archive solution implemented by our Database Analysts was flawed. Though it saved all the information, the reports used to retrieve certain sets of data contained errors and returned incorrect information. This is not good, but mistakes happen in business, and it's something that you just have to deal with.
However this is where the second problem creeps in. Having identified the first problem in late September, the database analysts didn't implement the fix until late October. They also failed to tell anyone outside their own team that there was a problem to start with, or that it had changed. As far as the rest of the company was concerned, everything had gone smoothly.
After some pretty intense grilling by me, the analysts admitted all this today. It means that about 80% of the work I have done over the past 14 weeks has been a complete waste of time, and I've got to start back from square one. It also means I've made a complete ***** of myself in front of a major customer.
So there you go. After considering long and hard, I've concluded that coaching or complaining is inappropriate, and the analysts must die. Their blood must be spilled, I'm afraid. So how can I conceal, or dispose of their bodies in a modern open-plan office? You're looking at typical software analysts (overfed, flabby sacks of ****) and there's four of them. Any suggestions? Feed them through the shredder? Thinly slice them, then file the slices under "****ing useless underhand sneaky cat****ers"?
In September we moved all our work from system A (because it was a pile of crap and riddled with faults) to system B. At the migration date, we saved a complete snapshot of system A's databases and reports in a "Business Objects" universe to act as an archive, so that when we identified problems in system B we could see what was the cause under system A, and fix it. Simple, right?
There were just two problems. Firstly, the archive solution implemented by our Database Analysts was flawed. Though it saved all the information, the reports used to retrieve certain sets of data contained errors and returned incorrect information. This is not good, but mistakes happen in business, and it's something that you just have to deal with.
However this is where the second problem creeps in. Having identified the first problem in late September, the database analysts didn't implement the fix until late October. They also failed to tell anyone outside their own team that there was a problem to start with, or that it had changed. As far as the rest of the company was concerned, everything had gone smoothly.
After some pretty intense grilling by me, the analysts admitted all this today. It means that about 80% of the work I have done over the past 14 weeks has been a complete waste of time, and I've got to start back from square one. It also means I've made a complete ***** of myself in front of a major customer.
So there you go. After considering long and hard, I've concluded that coaching or complaining is inappropriate, and the analysts must die. Their blood must be spilled, I'm afraid. So how can I conceal, or dispose of their bodies in a modern open-plan office? You're looking at typical software analysts (overfed, flabby sacks of ****) and there's four of them. Any suggestions? Feed them through the shredder? Thinly slice them, then file the slices under "****ing useless underhand sneaky cat****ers"?
Comment