Yes, I do. The reason why is because I am a "how things work" kind of a person and as a reverse engineer and foreward engineer, I'm having to figure codebases out all the time. The one's without documentation can be a real pain and waste a lot of time. I don't get how someone can spend a year or two writing a massive application and then have absolutely no documentation about it... It baffles my mind. And I say that coming from the perspective of actually *enjoying* turning assembly language into higher level languages or just analyzing assembly and machine code directly. Even though I love reverse engineering and I am never given a documentation for malware from the malware authors, I still believe that code up in a repository online and especially code developed professionally should have a documentation.
I sort of agree with the concept of "the code should be self-documenting" but the reality is that most of the time, the code is not self-documented well enough to completely avoid a documentation and having a full documentation which is also indexed and displayed properly can save a lot of precious time for a library user. Another argument for this in a professional codebase is, what happens when the devs quit or move on who made the original codebase and nobody knows how it works? This is another reason for docs. Docs, docs, docs!