Quote

However, writing software without defects is not sufficient. In my experience, it is at least as difficult to write software that is safe - that is, software that behaves reasonably under adverse conditions.

The reality of most software development is that the consequences of failure are simply nonexistent.

As a rule, software systems do not work well until they have been used, and have failed repeatedly, in real applications.

Writing software is a very intense, very personal thing. You have to have time to work your way through it, to understand it. Then debug it.

There are two ways to write error-free programs; only the third one works.

We are built to make mistakes, coded for error.

You fail only if you stop writing.

Writing software that's safe even in the presence of bugs makes the challenge even more interesting.

An error doesn't become a mistake until you refuse to correct it.

If you don't fix latent failures in your system, you're asking for trouble.