> It's not like programmers are immune from making such errors.
Too true. It wasn't that long ago that the programmers at The Knight Capital Group nearly sent the company broke with their $430 million programming glitch.
Except that wasn't a programming glitch, it was an operations glitch. They accidentally deployed a test trading partner for their real trading app to the real world.
So when I accidentally enter the wrong rate into the spread sheet everyone calls me an idiot and tells me I should leave the programming to people who know what they are doing.
But when a programmer I accidentally promotes test code to production, it's just an accident.
That is exactly the point the OP that I replied to was trying to make.
When someone else fucks they are stupid and they don’t know what they are doing, but when the coders fuck up it's always someone else that is at fault. Please give me a break!
Given that most spreadsheets only have one enrivonment (PROD), this class of error isn't likely. However, as the grandparent says, this means testing is equally unlikely.
Too true. It wasn't that long ago that the programmers at The Knight Capital Group nearly sent the company broke with their $430 million programming glitch.
http://topics.nytimes.com/top/news/business/companies/knight...