[0] http://www.wired.com/threatlevel/2008/09/six-year-old-st/ [1] http://www.vanityfair.com/business/2013/09/michael-lewis-gol... [2] http://www.ted.com/talks/kevin_slavin_how_algorithms_shape_o...
[0] http://www.wired.com/threatlevel/2008/09/six-year-old-st/ [1] http://www.vanityfair.com/business/2013/09/michael-lewis-gol... [2] http://www.ted.com/talks/kevin_slavin_how_algorithms_shape_o...
Could we stop with the vapid generalities? Obviously some people on Wall Street don't, but that doesn't mean it's universal.
http://www.wired.com/threatlevel/2008/09/six-year-old-st/
Hmm, a 5 year old story abut a trading mistake caused by human error, where someone didn't realize that an old story was no longer current because of a weakness in Google News's crawling procedure? This has nothing to do with software on wall Street and doesn't support your argument in the least. I think you should go back and reread it.
I think it is fair to say that 99% of the problems are on the client side... at least, that is how I made my bonus ;)
I always loved it when 10@100 became 100@10.
Granted, if we're talking about physically destroying infrastructure as opposed to just hacking, then I'd have to agree with you.
One thing to note is that many of the critical components on the electrical grid is controlled over the network. When I used to build tools for the electricity trading desk, we were handling market bids/asks and scheduling of the power plants.
Here's an example of the stuff that we were dealing with. This is the real time settlement point prices for ERCOT (the grid network in Texas): http://www.ercot.com/content/cdr/html/real_time_spp
We had systems that lay out prices that we were willing to turn on and ramp up power plants. If prices hit a certain point, we were committed to delivering that power. We made these decisions based on economics of the power plant (gas plant vs nuclear vs wind) and other factors (such as weather , time of day, whether the Cowboys were playing that day).
Anyways, my point is that all these systems are interconnected and rather complex. It doesn't take much for an error in one place to bring down a major part of the system.
Take a look at the 2003 Blackout: http://en.wikipedia.org/wiki/Northeast_blackout_of_2003
As with any engineering, you're never going to factor away all the breaks. You need to build a system that assume things will break and ensure that it's not catastrophic.
Also, I don't think it's fair to say that Wall Street doesn't understand software. There are some very smart people doing solid engineering there. Neither one of the footnotes that you had in your post support your statement that Wall St doesn't understand software.