Hmm, your post reads like a software ad for ankhor flowsheet. Interestingly, your user name "FeelYourDataFlow" is the claim on ANKHOR's web site.
So I guess your remarks on SPSS or Rapidminer, two of your direct competitors, are not really believable.

Flow-based Programming reminds me very much of current data mining suites like IBM SPSS Modeler or RapidMiner. The prefered way to model an analysis is to build a graphical flow chart using various building blocks connected to one another. Those high-level blocks can be as diverse as data transformations (filtering, aggregation) or data mining algorithms (decision tree, regression analysis).
The input for the analysis usually comes from one or many database systems. The output is usually also written to databases. FBP makes it very easy even for non-experts to build data mining analyses using these tools.

Reminds me of GLaDOS - "There's science to be done" :)

Shufflepuck Cafe, anybody?

I think, the professor in TFA is pretty much wrong. For a reality check, please look at this Wikipedia link. It describes the current research status in the field of object recognition, a typical task in computer vision. From the article, it should become clear that there are numerous approaches to the problem, but there is not one really capable approach that solves the problem. This is independent of computing power - we just don't know yet how to make a machine recognize non-trivial objects under real-life conditions, not matter how many CPUs it has. This fact currently limits the development of autonomic cars already.

According to Quantum_decoherence, there is no superposition of quantum states. As the radioactive element interacts with the cat and the box, its decoherence time becomes very short, so the wave function collapses almost instantly. The cat is either dead or alive, but there is no extended state of superposition.

In a situation where your company outsources code generation to some external IT consultancy, it might be beneficial for that external developer not to document his code. After all, who are they going to call when they need to understand the code or extend its functionality?
This also work down the road - if they should get several offers for future coding work in an RFP, the original programmer can still price very aggressively, as he knows all the pitfalls of the solution that he wrote in the past.

"I say we take off and nuke the site from orbit. It's the only way to be sure. " - a story right out of Hollywood :)