People that write this sort of "If you have to write comments your code sucks" commentary are almost always the ones laying down new code. They're the grizzled

People that write this sort of "If you have to write comments your code sucks" commentary are almost always the ones laying down new code. They're the grizzled veterans who don't think about the junior guys that have to update their code a year later and go "???" when they attempt to fix some subtle bug. As I'm sure will be repeated over and over, comment the why, not the what or the how.