"Unofficial" documentation can serve needs that are neglected by the official docs, even if only by offering a different point of view. I can't speak to Python

"Unofficial" documentation can serve needs that are neglected by the official docs, even if only by offering a different point of view. I can't speak to Python specifically, but to make an analogy, a microcontroller that I'm working with right now is documented by a 3500 page manual that requires a fair amount of expertise just to know what to look for. But a seasoned embedded dev might be just fine with that, and annoyed by anything simpler. On the other hand, I can make headway by using the Arduino API and boatloads of online documentation in the form of blogs, tutorials, StackOverflow, etc. Likewise, nobody knows how to write technical documentation that's readable by everybody. In the case of Python, the official docs are typically the last place where I'd look for stuff, given the quality of documents such as this cheat sheet. There's still a need for authoritative "developer" documentation, but not for me. The diversity of Python developers, from hobbyists to pro's, justifies a similar diversity of documentation.