It's better to wait for a productive programmer to become available than it is to wait for the first available programmer to become productive.
The programmer, like the poet, works only slightly removed from pure thought-stuff. He builds his castles in the air, from air, creating by exertion of the imagination. Few media of creation are so flexible, so easy to polish and rework, so readily capable of realizing grand conceptual structures.
Most good programmers do programming not because they expect to get paid or get adulation by the public, but because it is fun to program.
Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.
A computer is a stupid machine with the ability to do incredibly smart things, while computer programmers are smart people with the ability to do incredibly stupid things. They are, in short, a perfect match.
Theory is when you know something, but it doesn't work. Practice is when something works, but you don't know why. Programmers combine theory and practice: Nothing works and they don't know why.
A happy programmer is a productive programmer. That's why we optimize for happiness and you should too. Don't just pick tools and practices based on industry standards or performance metrics. Look at the intangibles: Is there passion, pride, and craftmanship here? Would you truly be happy working in this environment eight hours a day?
The trouble with programmers is that you can never tell what a programmer is doing until it's too late.
Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris.
If you want to set off and go develop some grand new thing, you don't need millions of dollars of capitalization. You need enough pizza and Diet Coke to stick in your refrigerator, a cheap PC to work on and the dedication to go through with it.