#feature quotes

... the cost of adding a feature isn't just the time it takes to code it. The cost also includes the addition of an obstacle to future expansion. ... The trick is to pick the features that don't fight each other.

There are features that should not be used.
There are concepts that should not be exploited.
There are problems that should not be solved.
There are programs that should not be written.

Programming languages should be designed not by piling feature on top of feature, but by removing the weaknesses and restrictions that make additional features appear necessary.

It's not a bug - it's an undocumented feature.

At any particular point in time, the features provided by our programming languages reflect our understanding of software and programming.

Normal people believe that if it ain't broke, don't fix it. Engineers believe that if it ain't broke, it doesn't have enough features yet.

For now, we really need to learn to be like doctors. They are able to say, quite comfortably and confidently and with conviction, "These things are never certain." Doctors seldom if ever state with certainty what the outcome of any procedure might be. Yet software managers, operating in a far less disciplined and less data-driven environment... blithely promise features, dates, and outcomes not especially susceptible to prediction.

Yes, features do sell products, but only if they actually work!

The hardest part of design... is keeping features out.