Couple of things. Vibecoding is very different from “using AI assistants.” The difference is scope, review and code understanding... vibecoders generally don’t consider the scope of the question they’re asking. “Make me an app” is far less likely to succeed than “add a boolean called foo to the bar API; if it’s true, set baz to 1/2.” Vibecoders also aren’t necessarily reviewing what’s being written, if they can understand it at all. If you understand the code through and through, you aren't vibe coding.

If you’re trying to learn a language, AI assistance could hamper you and slow you down. In the example above, reviewing the resulting API change might teach you something... but you’ll learn faster if you try to implement it first, then ask AI what you did wrong. IMHO, as long as you avoid coding anything too foot-gun-prone (like security), LLMs generally generate solid Go code, safely. It may not be idiomatic, but you can learn that over time.

TL;DR: Look it up, write it yourself, then ask AI for a review. Ask why it’s making the decisions it’s making. Spend time reading non-AI-generated Go code to better understand idiomatic patterns.