The structure of software systems tend to reflect the structure of the organization that produce them.

Software is usually expected to be modified over the course of its productive life. The process of converting one correct program into a different correct program is extremely challenging.

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

It turns out that style matters in programming for the same reason that it matters in writing. It makes for better reading.

JavaScript is the only language that I'm aware of that people feel they don't need to learn before they start using it.

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.

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.