I would agree, but it is normal to have badly written documentation. If more developers treated documentation as seriously as code then I would agree, but its normal for devs to frankly hate documentation. All too often the devs talk in domain terms that assume that you as a newbie understand those terms.
Documentation gives* information on how to use the library, how it is supposed to work, its expected behaviour, its quirks and exceptions. Written examples are a staple of good documentation but they will never substitute it for me, I find hard and against myself to use a library dumbly copy-pasting code without an organic explanation on what I am doing.
Assuming it is a well written library I don't have to go into the lib code, but I write my own little examples to try it out - after having read the docs and the provided examples.
And I keep the code for future reference.
This, too, is my favorite method. I put together small sections of code and verify that the library responds as expected, based on my understanding of the documentation and the published examples. When my examples fail, I review what I have read and the code I have written, then try again. If my attempts continue to fail, I email someone more knowledgeable for some help.
I think its because of the way the survey was phrased as "understand a new library". Asking a Q. online or in a forum is usually reserved for after you've become acquainted with the code for awhile but now are dealing with some problem that you need help on.
Asking a Q. online or in a forum is usually reserved for after you've become acquainted with the code for awhile but now are dealing with some problem that you need help on.
or for the lazy morons that don't even bother in trying to understand it and prefer to try to fool you to do their homework for them
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.