Most programming languages contain good parts and bad parts. I discovered that I could be better programmer by using only the good parts and avoiding the bad parts.

Just because something is a standard doesn’t mean it is the right choice for every application. Like XML, for example.

People who should be the first to recognize the value of an innovation are often the last.

Computer programs are the most complex things that humans make.

Good architecture is necessary to give programs enough structure to be able to grow large without collapsing into a puddle of confusion.

We see a lot of feature-driven product design in which the cost of features is not properly accounted. Features can have a negative value to customers because they make the products more difficult to understand and use. We are finding that people like products that just work. It turns out that designs that just work are much harder to produce that designs that assemble long lists of features.

It turns out that strong typing does not eliminate the need for careful testing. And I have found in my work that the sorts of errors that strong type checking finds are no the errors I worry about.