So rather than jump in and start adding documentation you blast the developers, who are offering this stuff free and without warranty or implied fitness for any purpose?<p>You can contribute by adding documentation where you see it lacking, especially if you have domain specific knowledge that would help others.<p>Or you can blast the entire project, not help, and go write your own. The thing that bothers me is that if you know enough, and it&#x27;s mostly a teaching tool (my understanding from other comments), you could greatly improve the situation for the next guy by providing your enlightened input on the subject in the form of documentation. So the whole damn community loses out on your hard-earned understanding.<p>Meanwhile, 10 years from now, your project will be replaced, and if NLTK is really a teaching tool, you won&#x27;t even be a footnote (because teaching tools don&#x27;t die unless a whole field dies).<p>This smacks of the kind of &quot;bubble&quot; Silicon Valley entitlement that I can&#x27;t quite wrap my head around (I know, author isn&#x27;t in SV, I just see this kind of crap coming from there).