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.'"
So a sometime programmer likes to think he is better than people who don't know how to program at all? As a fulltime programmer (which apparently puts me higher in the hierarchy) I think that is just a bit silly.
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
"Create Huge Row"
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.
This is the state of rail "privatisation" in the UK today.
Just to expand on that, "Privatisation" is a UK concept that seeks to combine the efficiency and value for money of government with the social responsibility and long-term vision of big business.
It's what you get if you spend so much time flip-flopping between socialist and capitalist governments that even the parties forget which is which.
In a survey of 100 programmers, 111111 thought that duck-typing was a good idea.
Get all those stupid computers off people's desks! Things were much better when you had to go to a programmer in order to get software to do anything!
And (not incidentally) it would eliiminate all the productivity that's lost to Slashdot!
Your sarcasm is unwarranted. This is a nice story for us programmers because it's just the kind of anecdote that makes businesses seriously consider hiring more professional programmers. Nobody is suggesting you need custom software for everything.
"Create Huge Row"
And the Daily Mail dedicated several Columns to it.
The submitter is suggesting — no, make that "claiming" — that spreadseets are dangerous because they allow "non-professionals" to program. Now, spreadsheets are the original "killer app" for PCs. Huge numbers of CP/M-based systems were sold just to run VisiCalc, and this probably had a lot to do with IBM biting the bullet and getting into the desktop computer business, with results that reverberate to this very day and the forseeable future. Alan Kay, one of the inventors of OOP and GUI, cites spreadsheets as a tool that turn ordinary users into programmers. Attack spreadsheets, and you attack the entire idea of user-centric programming. The submitter's attitude is reminiscint of the pre-Woz era, when you had to negotiate with your programming staff to do even the simplest computing and programmers were known as "High Priests of a Low Cult". There's a lot of room for sarcasm here.
More than I thought to use. I also could have been sarcastic about the assumption that "hire a pro" is a magic bullet for avoiding fuckups. Really? "Professionals" never make stupid, multimillion-dollar mistakes? Get real.
"Have somebody check your work" is the applicable lesson here. "Hire a pro and you're safe." is just bullshit.
Because without some sort of proof of a sound business model, a company can underbid/overbid (underbid on cost, overbid on the fees they will pay the government) just to get into the market. Then they can run the service into the ground, suck any money they can out into 'consulting fees' and other such expenses that end up in the investor's pockets, and then just go bankrupt. The government gets left holding the run down remains, and suddenly all the trains stop.