When I attended the University of Leiden Software-Development was in its infancy. In 1969 just a few people were programming for the simple reason that the amount of computers was very low. It took a lot of time (many weeks), intelligence and perseverance to create a small working software-program. At that time the effect of a software-program on other people was very low. Software-programs were used by the programmers themselves to solve their own problems. When User-Interfaces, Databases and Telecommunication appeared it became possible to create software for Many Non-Programmers, Users. The software-systems got bigger and programmers had to cooperate … Continue reading About (Software) Quality
In the beginning of Software Development Programmers just Programmed. They did not use any method. The program was punched on a stack of cards and the computer executed the code. It took many days to get a small program running. In the early 1980s text edit]]><![CDATA[ors were introduced. In this stage somebody else called an Analyst wrote down Specifications and the Programmer transformed the specifications into a Program. The Programmers and Analysts had to fill in forms with a pencil. The forms were typed by a central department and returned to them for correction. Much later programmers and analysts were … Continue reading About Model Driven Software Development
Metaphysics is a theory of being in itself, of the essence of things, of the fundamental principles of existence and reality. A major part of Metaphysics is concerned with the Static Part of the Reality, Being (Ontos, Ontology). The main issues of Metaphysics can be simply derived by playing with the verb to-be. Behind Ontology (Being) is the verb to Be. The noun Being is-a-State-of to Be. When we take the first-derative, the difference of Being, Being becomes Becoming. When you apply Causal Reasoning you have to find out Who is the Cause of the change of Being to Becoming. … Continue reading About Ontology
A major part of our activities have to do with “Not-Knowing”. We are constantly talking with others about “What we don’t Know”. We are speculating and are hoping that others know. Humans are wondering creatures. The situation becomes more complicated when we meet people who are convinced they know but really don’t know. We believe them because they look like “People who know”. They are to be trusted. When we understand what they are talking about we spread the news and in due time many other people “know”. The moment of Truth is when we Apply the Knowledge. Suddenly Everything … Continue reading About Programming Conversations and Conversations About Programming
When you lend somebody something you assume he (or she) will give the item back in due time. To lend you have to Trust somebody. There are many ways to create a trusted relation. When a long term trusted relationship grows out of a long chain of interactions the Iterated Prisoners Dilemma is at stake. The Chinese are the Masters of Playing this Game. In some situations it is very clear that a try-out is not necessary. If we look at the cultures of the Earth we can see that the concept of Family or Tribe more or less guaranties … Continue reading About Virtue and Wisdom
Another new hype-term is the Mash-up. A Mash-up is a new service, that combines functionality or content from existing sources. In the “old’ days of programming we called a Mash-up a Program (now Service) and the parts of the Program Modules. Modules were reused by other Programs. We developed and acquired libraries that contained many useful modules. They did not document the software and used many features of the operating system that interfered with other programs. The very old software programs created the Software Legacy Problem. Another interesting issue that has to be resolved is Security. Mash-ups … Continue reading About Mash-Ups
Edsger Wybe Dijkstra (1930-2000) was a Dutch computer scientist. He received the 1972 Turing Award for fundamental contributions in the area of programming languages.
He was known for his low opinion of the GOTO-statement in computer programming culminating in the 1968 article “A Case against the GOTO Statement” (EWD215), regarded as a major step towards the widespread deprecation of the GOTO statement and its effective replacement by structured control constructs such as the DO-WHILE-LOOP. This methodology was also called Structured Programming.