A common case for me is 'use this library/package to complete the task to do this thing', I want to write the code that uses the package, the package API is opaque, it speaks in a language that makes sense if you have been playing with a dozen different similar packages, it isn't going to be useful for any other project there is something about this project that makes this package a requirement.
I've come to recognize that I have to give myself permission to read all the docs on the package, and then read large chunks of the discussion amongst enthusiasts of this type of package, then read the original docs again, and contextualize what they say into what I need to do in order to get the package to do what I want. If I don't give myself permission I perceive all of that time as wasted just trying to get the package to do what it does and I need it to do so that I can forget it and move on.
So painful.