1. Google if someone had the same problem and fixed it.
2. Hope you're using OSS software and simply browse the source to find answers.
The second approach is a bit slower at first, but after you dismantled a bunch of repos it becomes natural, you get faster and the answers you find are more reliable.
Having done enough of the second approach, I find it hard to understand why people do the first -- why see what people wrote about what something does when you can just see what it does. Even man pages are some amount of here say, versus inspecting the code.
That said, I do web search some specific terms frequently to get to certain documentation that I trust, SMS search is the easiest way to get there consistently.
There's plenty of things that I can't write that I can understand. Even if I can't understand it, I can look and see what it's expecting for arguments and figure out why it doesn't like what ever thing I sent that was probably dumb.
2. Hope you're using OSS software and simply browse the source to find answers.
The second approach is a bit slower at first, but after you dismantled a bunch of repos it becomes natural, you get faster and the answers you find are more reliable.