4 ms·
Most docs for technical projects are written that way these days. The author of an api, project or solution will assume an unquestioned adoption "because it's f
by thelastidiot 8y ago
Most docs for technical projects are written that way these days. The author of an api, project or solution will assume an unquestioned adoption "because it's free" from the randome audience with no specifics on how they are solving and more importantly what's different from other cases. I don't know if this is by laziness and writing procrastination, but assuming that your users will know as much as you do on your journey to assemble a solution has become a frustration when I discover new projects like this one.
- RhodesianHunter 8y agoLikely has a lot more to do with the fact that the intersection between the population that can create such projects and the population that can write clear effective documentation is exceedingly small.
- bonesss 8y agoI would also point to Paul Grahams insight around hackers and painters[0]: the population who wants to create such projects is fantasizing about coding, hacking, publishing, bug squashing, and launches. Documentation isn't necessarily pulling them to their PC after a heavy dinner. - [0] http://www.paulgraham.com/hp.html http://www.paulgraham.com/hp.html
- pests 8y agoI feel as if you have a bit of a tone against these authors. Would you rather the software not exist at all?