In my experience, you either have encapsulation and abstraction or you have neither. There is no middle ground.

A typical software project can present more opportunities to learn from mistakes than some people get in a lifetime.

The primary purpose of software estimation is not to predict a project's outcome; it is to determine whether a project's targets are realistic enough to allow the project to be controlled to meet them.

Engineering is the application of scientific principles toward practical ends. If the engineering isn't practical, it's bad engineering.

95% on content and the computer language remains the same.

In software, the chain isn't as strong as its weakest link; it's as weak as all the weak links multiplied together.

Trying to apply formal methods to all software projects is just as bad as trying to apply code-and-fix development to all projects.