[gcmrtc]

> Honestly? Not everyone wants (or should have) to do that in order to touch some Go code

For hobby projects maybe, if it's part of your job you should know what you're doing and read the fine manual (basic documentation in this case).

[filleduchaos]

That literally is the point, thank you for restating it explicitly. Not everybody is trying to get a job as a Go developer. People who just want to make a change or two to a tool that they use, to follow what someone else is doing, or to even just get a quick feel for the language without being treated like an absolute beginner to programming are users too and there is nothing wrong with making resources that are helpful for them.

[karolist]

Ideally you'd have someone more experienced to do a code review and correct your mistakes if it's just a one off change, Go is not hard to pick up and compiler gives good hints usually.

[filleduchaos]

> Ideally you'd have someone more experienced to do a code review

I cannot stress enough that not all programming occurs in a work or even social context.

Besides, I did not say Go is hard to pick up. I said people should not need to read the entire manual, so to speak, to do things involving Go or any other language or tool. Cheat sheets like the linked article that outline the language in terms of "things you need to know as someone who already programs extensively" are thus actually quite helpful. That is all.