I think that a lot of programmers are ignoring an important point when people talk about reducing code repetition on large projects. Part of the idea is that large projects are intrinsically *wrong*. That you should be looking at making a number of smaller projects that are composable, even if you never end up reusing one of those smaller projects elsewhere. -- Dan Nugent

What I didn't understand was that the value of some new acquisition wasn't the difference between its retail price and what I paid for it. It was the value I derived from it. Stuff is an extremely illiquid asset. Unless you have some plan for selling that valuable thing you got so cheaply, what difference does it make what it's "worth?" The only way you're ever going to extract any value from it is to use it. And if you don't have any immediate use for it, you probably never will. -- Paul Graham

An expert is, according to my working definition "someone who doesn't need to look up answers to easy questions". -- Eric Lippert.

Write it properly first. It's easier to make a correct program fast, than to make a fast program correct. -- http://www.cpax.org.uk/prg/

[Innovation] comes from saying no to 1,000 things to make sure we don’t get on the wrong track or try to do too much. We’re always thinking about new markets we could enter, but it’s only by saying no that you can concentrate on the things that are really important. -- Steve Jobs

Beware of bugs in the above code; I have only proved it correct, not tried it. -- Donald Knuth

If you do what you always did, you will get what you always got. ~Anonymous

I attribute my success to this: I never gave or took any excuse. –Florence Nightingale

First, have a definite, clear practical ideal; a goal, an objective. Second, have the necessary means to achieve your ends; wisdom, money, materials, and methods. Third, adjust all your means to that end. –Aristotle

No one can make you feel inferior without your consent. ~Eleanor Roosevelt