Spreadsheet Blamed For UK Rail Bid Fiasco
First time accepted submitter Bruce66423 writes "As a sometime computer programmer who was always very sniffy about the quality of the stuff being knocked up by amateurs aka power users, the current claim that it was a messed up spreadsheet that caused a multi-million pound fiasco is very satisfying. 'The key mechanism... mixed up real and inflated financial figures and contained elements of double counting.'"
For those of us who speak English as a first language, here's a translation:
"A messed-up spreadsheet caused a multi-million-pound fiasco."
I think it refers to government financing for some sort of rail transport project in England, but I'm not as sure about that part.
I suspect there are better ways to get all of the above, but that is irrelevant. Does the submitter think that people who use other programming languages do not make such catastrophic mistakes? I think history says otherwise:
https://en.wikipedia.org/wiki/Knight_capital
https://en.wikipedia.org/wiki/Ariane_5_Flight_501
Bugs can be costly, regardless of whether those bugs are in spreadsheets or Ada programs.
Palm trees and 8
Spreadsheets -- well, Excel really -- are inescapable in business.
I know personally of complex multimillion dollar deals in the oil and gas business involving buying and selling entire refineries and gas pipelines where the numbers were all worked out on a spreadsheet.
The insurance industry lives on the spreadsheets put together by the actuaries.
The only consistent reason I've seen for Excel users will give up their rows and columns and have bespoke software created is when the dataset gets cumbersomely large. A secondary reason is when the kinds of calculations needed can't be cobbled together with Excel's function and macro tools. Even then, it's not unheard of for users to demand summary/aggregate reports and analytics that they then copy the numbers from into their spreadsheet to do their scenarios.
Just keep in mind the next time you hear about big money moving around in some deal -- somewhere someone probably had a pivot table for that.
It's funny though how the IT department always has to take over and maintain the garbage spreadsheets and databases put together by the "power user" in various organizations when that person leaves or is transferred. We inherit this utter crap and then are expected to maintain things that never should have been built in an end user computing platform like Excel or the like.