That's a compelling case for commoditization of talent, but in the end I think it's just a heuristic improvement. It gets you pretty far, but at the end of the day you still have huge teams of PhDs and M.Archs doing the actual engineering. (If that was commoditized it would be a scary world indeed!)
Let's see if it's still standing a couple decades from now.
> Let's see if it's still standing a couple decades from now.
I didn't realise that it was solely teams of skilled engineers and artisans doing the riveting on Empire State back in 1930.
I seriously doubt 30's margins are still being applied.
A little bit of Darwin, on why things are the way they are.
Frankly, anyone flying at a low speed and very low altitude (which I define here as few hundred feet) with jet engines at idle needs to have their head examined. Whatever the software did or didn't do, the pilots knew all of these details and that with their craft's low energy level and the engines spooled down they had little or no margin for error, their's or the new (less than one and half years since first flight) fly-by-wire software.
http://news.ycombinator.com/item?id=968013
You can test the depth of CS for yourself when you take your first formal methods course.
> is that it's the only discipline that eschews paradox.
> Even mathematics has reams of unanswered questions and
> potential paradox in its core philosophy. In Computer
> Science, there's none. It's assumed that all of it is
> pretty much solved and your job as an undergraduate is
> to just learn to get a job in this totally solved area
> of expertise.
Zed is confusing software engineering with computer science. CS is a branch of applied mathematics, and it's not different from mathematics. There are unsolved problems and plenty of areas that require further research.