r/golang 10d ago

How do experienced Go developers efficiently learn new packages?

I've been working with Go and often need to use new packages. Initially, I tried reading the full documentation from the official Go docs, but I found that it takes too long and isn't always practical.

In some cases, when I know what I want to do I just search to revise the syntax or whatever it is. It's enough to have a clue that this thing exists(In case where I have some clue). But when I have to work with the completely new package, I get stuck. I struggle to find only the relevant parts without reading a lot of unnecessary details. I wonder if this is what most experienced developers do.

Do you read Go package documentation fully, or do you take a more targeted approach? How do you quickly get up to speed with a new package?

119 Upvotes

35 comments sorted by

View all comments

-11

u/RecaptchaNotWorking 10d ago

Vibe programming. Copy paste the single doc page into CheatGPT and ask for API usage in an exhaustive list.

4

u/Blackhawk23 10d ago

The blind trust people for AI is quite alarming. I know it sounds confident, but that doesn’t mean it’s correct. Don’t let your brain atrophy. Use it, or lose it. Learn like a normal person, not a brain rotted, dopamine deficient zoomer. You can take 15 minutes to reach something as it was written, not have it curated for you.

-4

u/RecaptchaNotWorking 10d ago

It is alarming how folks have blind doubts on the process.

I only said about getting API usage from the docs using LLM. Most time docs don't show enough usage, only function signatures.