| Thank you for this!
I completely agree. Just a recent example (it's just AN example, there are probably way better examples than this one):
I started recently to code a website after years without putting my hands in web development. I went through some documentations of multiple lightweight frameworks for server side coding: 100% relies on the reader to know how to use the latest fancy-cool-kids-choice packet manager for the given language. If you do know by heart your brew-npm-composer-pacman-I-dont-know-what, good for you dear documentation writer -> not everybody does!! Which means that if, for some reasons, there is the slightest issue with any of the versions of the hundreds of dependencies your "basic application" requires, it means that the newcomer for your framework must found his.her way into a stack of tools and dependencies that is galactic in size. More than half of the documentation said that if you don't want to use the packet manager you can use a virtual machine or a container manager (Docker) 100% of the documentation I read started showing code to configure the project WITHOUT mentioning in WHICH files the code should go into -> it was implied!!! -> searching about the topic online made me realize I was not the only one, and the response from the helpers were actually very efficient and correct and were not part of the documentation! 100% of the documentation included non-self sufficient information to have something working and running -> proof is, search for one the problems on whatever search engine -> led to hundreds if not thousands of results of people asking their ways into having the "Getting Started tutorial" to actually work!!! |