Exactly what we were saying the other day and getting slammed for in the thread on Agile and developers leaving (in response to somebody mentioning "working code over comprehensive docs").

Code or docs that explain the how and not the why are pretty subgood.

Code is better than docs at explaining the how of a program, so it makes sense to have sparse comments in certain places. The why, though, is much better served by a few thorough high-level documents that help give the framework and context for a bit of software.