Internal vs External Quality

Try explaining the difference to any kind of manager who hasn't come up from the "trenches of programming" (http://martinfowler.com/bliki/TradableQualityHypothesis.html)

Coders@Work

"...Then there was another book that everybody thought was the greatest thing ever in that same period—Design Patterns—which I just thought was crap. It was just like, programming via cut and paste. Rather than thinking through your task you looked through the recipe book and found something that maybe, kinda, sorta felt like it, and then just aped it. That’s not programming; that’s a coloring book. But a lot of people seemed to love it. Then in meetings they’d be tossing around all this terminology they got out of that book. Like, the inverse, reverse, double-back-flip pattern—whatever. 
Oh, you mean a loop? OK." - jwz

Übergeneralization

Every once in a while, when writing code, you may find yourself trying to write it in such a way that it can be "easily extended" and solve a whole lot more than originally intended. 

Have a look at this: http://chaosinmotion.com/blog/?p=622 to see what I mean.

How Nescape became Mozilla

Project CodeRush, a good documentary film on how Mozilla was born: http://www.youtube.com/watch?v=u404SLJj7ig&feature=player_embedded