1

Don’t live with broken window

2

Stone Soap: Work out what you can reasonably ask for. Develop it well. Once you’ve got it, show people, and let them marvel. Then say “of Course, it would be better if we add…”

3

September, 1752 had only 19 days

4

Program for the general case, and put the specifics somewhere else

Put Abstractions in Code, Details in Metadata

5

Even if the architecture required two-digit years for data input, reporting, and storage, there should have been an abstraction of a DATE that “knew” the two digits were an abbreviated form of the real date

Abstractions live longer than details

6

We are driven to find our bugs now, so we don’t have to endure the shame of others finding our bugs later

7

Test state coverage, not code coverage

8

Documentation and code are different views of the same underlying model, … Treat documentation with the same care you treat code, and the users (and the maintainers who follow) will sing you praises

9

Gently exceeds your users’ expectations.

10

Sign your work. People should see your name on a piece of code and expect it to be solid, well written, tested, and documented. A really professional job. Written by a real professional.