Scroll down
Computer science education cannot make anybody an expert programmer any more than studying brushes and pigment can make somebody an expert painter.
Given enough eyeballs, all bugs are shallow.
Given enough eyeballs, all bugs are shallow (e.g., given a large enough beta-tester and co-developer base, almost every problem will be characterized quickly and the fix obvious to someone).
(Lesson 8 in The Cathedral and the Bazaar)
Lisp is worth learning for the profound enlightenment experience you will have when you finally get it; that experience will make you a better programmer for the rest of your days, even if you never actually use Lisp itself a lot.
"How to Become a Hacker"
Publishing a theory should not be the end of one's conversation with the universe, but the beginning
The Cathedral and the Bazaar
While I don't claim to be a great programmer, I try to imitate one. An important trait of the great ones is constructive laziness. They know that you get an A not for effort but for results, and that it's almost always easier to start from a good partial solution than from nothing at all.
If you have the right attitude, interesting problems will find you.
Smart data structures and dumb code works a lot better than the other way around.
The most obvious common ‘personality’ characteristics of hackers are high intelligence, consuming curiosity, and facility with intellectual abstractions. Also, most hackers are ‘neophiles’, stimulated by and appreciative of novelty (especially intellectual novelty). Most are also relatively individualistic and anti-conformist.
Ugly programs are like ugly suspension bridges: they're much more liable to collapse than pretty ones, because the way humans (especially engineer-humans) perceive beauty is intimately related to our ability to process and understand complexity. A language that makes it hard to write elegant code makes it hard to write good code.
