One thing that this book mentions (and which many people swear by) is "self documenting code". In my experience, I've found that: (1) good "self documenting c

One thing that this book mentions (and which many people swear by) is "self documenting code". In my experience, I've found that: (1) good "self documenting code" is typically written by programmers who care enough about documentation to write at least a high-level description of what their code is trying to achieve, what problems it is trying to solve. (2) programmers who swear by "self documenting code" usually write code that is anything but self-documenting. Their output is usually so gloriously complex that nobody apart from them can easily read and understand their code.