I came across this article where the author read the NodeJS docs, and came across interesting things which he never knew before.
I think it is a powerful thing to read the docs of a tool/library which you use. It will help in making better decisions while using the tool/library. What is your opinion?
I find it's easier to jump right in and only refer to the docs when I get stuck or need something. I'm too impatient to read the entire docs first except in rare circumstances (I read all of zeroMQ docs before using it... the docs are very well written and quite entertaining. I read all of redux-saga docs because the concepts were fascinating to me).
However, this practice has also bitten me. I jumped into Durandal two years ago for client-side SPA development and ended up doing a lot of things the hard way. Took a while to restructure the code to 'go with the grain'. But then, the Durandal docs (much like Webpack docs) are absolutely terrible.
That really depends. I have never read the whole jQuery documentation, even though I use it on a regular basis. On the other hand I have read the whole docs for VueJS (1), but never actually really used it. Whatever it takes to get the job done I guess.
I understand the sensation of reading docs and discovering new stuff, but I am only ever tempted to do that when I'm on the hunt for a good blog post (and I don't even have a blog).
j
stuff ;)
It depends, if I implement a protocol / library I read the documentation and parts of the code.
If it's an app based on a framework like react I take code examples and face the problems as I move along. And maybe after the first 3 prototypes I read the complete documentation so it sticks because I have built the synapses to remember them better.