On another note, how much proof of of NOT crashing in the next plane do you accept as tolerable for taking said plane? You seem to argue for 0%: we need to be absolutely sure that we are crashing this plane before we refuse to take it.If we survive 1 in a 100 flights, we shouldn't complain. We need to be absolutely sure that we crash this plane before we try to do something about it.
So yes, I'm sorry. The state of this part of science is such that all obvious issues have been addressed. Although far from perfect, the picture emerging is consistent with a climate that is quickly heating due to forcing by CO2. This CO2 is man-made by burning CO2 previously captured. To invalidate this whole, you will have to find non-obvious sources of error. This will require a lot of work, and, might not even be possible because you know, the overall picture might actually be roughly correct.
However the programming models that claim to be following this model want to take extremely complex modules (a database engine or GUI framework) and then just tie them together with a little syntactic glue. Plus they strongly discourage any programmer from creating their own modules or blocks (that's only for experts), and insist on forcing the wrong module to fit with extra duct tape rather than create a new module that is a better fit (there's a pathological fear of reinventing the wheel, even though when you go to the auto store you can see many varieties of wheels). And these are treated like black boxes; the programmers don't know how they work inside or why one is better than another for different uses.
And honestly, what's wrong with this? Complex modules such as database engines or GUI frameworks should be black boxes, with no need to look inside. What we're failing to do as a profession is to be able to clearly state what these black boxes are providing. So yes, I want to know that if I query this database on a field that hasn't got an index that it is O(n), instead of O(log(n)) if it has one. I truly don't care how they achieve that, and if they don't achieve what they claim, I would want to be able to sue and get another library.
What you're advocating is the status-quo. We don't really engineer our solutions so we need to have knowledge of each part of the solution. If you contrast this with real engineering: there every layer provides some form of guarantees. If you build a bridge, you know the forces steel products can withstand, and you pick your supplier of steel based on these guarantees. We don't do anything of the sort. We just pick at random and hope for the best. No engineering.
e^{\tau i} = 1.
As a corollary -- we did not need to actually understand much about how biological organisms swim to be able to build a submarine.
How do you know that that he isn't the prick that the media has made him out to be?
Who cares? You're just shooting the messenger. The media is simply trying to cover up the fact that they seized to be
In short, you either need an infinite amount of monkeys, or an infinite amount of time to produce Hamlet.
"More software projects have gone awry for lack of calendar time than for all other causes combined." -- Fred Brooks, Jr., _The Mythical Man Month_