So do I. I even write documentation for personal projects, as a manual to my future self. However, absolutely every team I've ever worked with held a majority v

So do I. I even write documentation for personal projects, as a manual to my future self. However, absolutely every team I've ever worked with held a majority view of documentation being unnecessary. Some even mentioned "code as documentation". In the end, they just kept finding justifications for not writing documentation or even proper code comments. Three months after some solution was written, they couldn't explain the thinking behind it or even all the deep dependencies and magic return values because the person who had written the solution had left the team. Even then they were unwilling to see how documentation would have helped. This repeated with every freaking team I have ever worked with. The only documentation any of those projects had was the one I created while figuring out the code base. I observed a fundamental laziness in written communication in many developers and to this day I find it puzzling. I sometimes write down a draft of some solution just by myself, like I would explain it to another developer. More often than not, this helps me in highlighting inconsistencies or errors in my thinking.