Things Every Programmer Should Know

I really enjoyed this article on sleep optimization that was posted on HN recently: http://brianmartinek.com/2013/08/22/three-simple-ways-that-i...

Finally, working out is a tremendous help. Especially if you can try to do a workout that maximizes the release of hormones like endorphins and testosterone.

Lots of good articles in there, though.

I have no problem emailing people to let them know of a feature they may not be aware of, but now that language feature is documented right there in our code base.

This is a good way of looking at it... as long as you remember that this shortfall is often gigantic, and usually includes why this approach is being used instead of other techniques (which may have been used and abandoned for good reason).

Code does not exist in a vacuum. You should write code not just to compile, but to be read by others. And many times, the actual code might be only 30% of the important stuff. A good project may very well be 2/3 comments, 1/3 code, because it should include the reasoning behind coding decisions, which is often quite complex, but crucial to understanding why the code is written as is, and to understanding how to properly extend it.

Without that kind of documentation, you're doing a tremendous disservice to future programmers who seek to maintain or add to the code -- or to yourself, often times, when you pick up code you wrote yourself two years ago.