Stupid and dangerous advice, too little documentation ALWAYS creates more problems and loss of time than too much Figuring out completely missing information i

Stupid and dangerous advice, too little documentation ALWAYS creates more problems and loss of time than too much Figuring out completely missing information is harder than understanding even what a bad comment really meant, and especially what an outdated one did (git...) Of course the right thing is indeeed to use code as expressive as possible, but then also to document carefully every useful thing that can't be explained by the code, and to keep the documentation up to date. Yes, the current tooling makes it harder than it could be to notice, find and track the documentation you need, but dealing with that is on average a lot better than omitting informations