Dear Friends,

What is the essential purpose of theoretical knowledge (of any science or engineering) comprising of theories, concepts, definitions, or methods? The essential purpose of theoretical knowledge is providing explanatory or predictive power, which is essential to gain deeper insights and understanding about problems, for example to address them. It is impossible to solve any scientific or technological problem by relaying on relevant theoretical knowledge that is flawed (e.g. misleading knowledge that creates flawed perception or alters our perception of reality). Hence, major software problems stood unsolved for decades due to flawed theoretical knowledge.

For example, every valid scientific or theoretical discovery in the history is a new knowledge that provided valid explanation to gain better and valid understanding. Any reseach efforts will be diverted into a wrong path (as soon as reseach efforts start relying on misleading knowledge), and the reseach efforts sooner or later inevitably ends up in a paradox, which will be filled with inexplicable contradictions or anomalies.

"The great enemy of the truth is very often not the lie — deliberate, contrived and dishonest — but the myth — persistent, persuasive, and unrealistic. Too often we hold fast to the cliches of our forebears. We subject all facts to a prefabricated set of interpretations. We enjoy the comfort of opinion without the discomfort of thought." ... John F. Kennedy

The very purpose of knowledge is to understand and gain insights or wisdom for example to solve problems, but not to confuse or mislead, which inevitably creates problems or prevent us from solving problems. Existing theories, definitions, concepts and methods for software components and CBPs (Component-Based Products) are flawed, and insidiously misleading, which not only created software crisis but also has been successfully prevented researchers from finding solutions for many decades.

Is he a scientist if he cannot understand this simple common-sense fact? - Using flawed or misleading knowledge inevitably creates problems or crisis. It is impossible to solve the problems (i) without realising the mistake (i.e. using invalid or misleading knowledge) and (ii) without acquiring valid knowledge. The definitions, concepts, or methods for so called components for software and CBPs are certainly flawed and insidiously misleading. In case of software, the insidiously misleading knowledge certainly preventing software researchers and scientists from understanding simple obvious valid knowledge that is essential to solve the problem (i.e. software crisis).

Existing flawed knowledge about so called software components and CBPs certainly satisfy this condition: Anything is an insidious lie, if it is misleading and caused a crisis and if it has successfully prevented research community for decades from finding the necessary truth (i.e. valid knowledge) that is essential to solve the problem (i.e. crisis).

In summary, is it difficult to understand this simple common-sense fact: Bad knowledge creates problems, and Good knowledge solves problems?

P.S: The two-page PDF provides obvious facts about (i) What is a CBP (Component-Based Product) that expose invidious lies that cased software crisis, and (ii) what are the inventions that are essential to build every software product as a CBP (i.e. by plugging-in optimal sized components).

Best Regards,

Raju Chiluvuri

More Raju Chiluvuri's questions See All
Similar questions and discussions