I think we may be thinking about this differently. I value reading the documentation of libraries that I'm using. I don't memorize it, but casually read over i

I think we may be thinking about this differently. I value reading the documentation of libraries that I'm using. I don't memorize it, but casually read over it to understand what's possible. I do not do this for everything, but if it's a piece of technology that I value, then it's probably a good idea to read the docs so that I'm not faced with "I did not know that it could do that" situation. The amount of times I've seen developers painfully code around something that was already supported in the library they're using is suprizing.