“Until we understand languages of communication involving humans as they are then it is unlikely many of our software problems will vanish.”

“Creating a modeling language that is also an executable language has long been a goal of the software community. Many years ago, in 1968 to be exact, while working with software components to successfully develop a telecommunications system, we created a modeling language that was the forerunner to UML. To model components we used sequence diagrams, collaboration diagrams, and state transition diagrams (a combination of state charts and activity diagrams). Our modeling language then seamlessly translated the component models into code. Each code component was in its turn compiled into an executable component that was deployed in our computer system. The computer system was a component management system—thus we had "components all the way down."”

“Until we invent telepathy, books are our best choice for understanding the rest of humanity.”

“Throughout the software life cycle, there are many decision situations involving limited resources in which software engineering economics techniques provide useful assistance.”

“The GNU GPL is not Mr. Nice Guy. It says "no" to some of the things that people sometimes want to do. There are users who say that this is a bad thing — that the GPL "excludes" some proprietary software developers who "need to be brought into the free software community."
But we are not excluding them from our community; they are choosing not to enter. Their decision to make software proprietary is a decision to stay out of our community. Being in our community means joining in cooperation with us; we cannot "bring them into our community" if they don't want to join.
What we can do is offer them an inducement to join. The GNU GPL is designed to make an inducement from our existing software: "If you will make your software free, you can use this code."”

“The biggest communication problem is we do not listen to understand.
We listen to reply.”

“The biggest communication problem is we do not listen to understand. We listen to reply.”

“In order to better understand object-oriented methodologies in general, it helps to understand the people who make up the "object-oriented community" itself. Far from being monolithic, there is a great deal of diversity within this community. Many object-oriented people, for example, seem to focus almost entirely on programming language issues. They tend to cast all discussions in terms of the syntax and semantics of their chosen object-oriented programming language. These people find it impossible (for all intents and purposes) to discuss any software engineering activity (e. g., analysis, design, and testing) without direct mention of some specific implementation language.
Outside of producing executable "prototypes", people who emphasize programming languages seldom have well-defined techniques for analyzing their clients' problems or describing the overall architecture of the software product. A great deal of what they do is intuitive. If they happen to have a natural instinct/intuition for good analysis or good design, their efforts on small-to-medium, non-critical projects can result in respectable software solutions.”

“The inability to isolate software components from each other is the main reason why many popular programming languages cannot be used for making robust system software.”

“Computers are not very smart. They don't understand human language, so we have to tell them what to do in a language that both humans and computers can understand.”