4 ms·

A tip from someone that just recently started using Go: read the spec! I wasted some time early on trying to learn things that are very clearly and simply spell

by staunch 13y ago

A tip from someone that just recently started using Go: read the spec! I wasted some time early on trying to learn things that are very clearly and simply spelled out in the spec. The Tour + Spec is really all you need if you're a somewhat experienced programmer. The spec is well written and tiny compared to most languages, and it's probably the only thoroughly accurate and complete Go reference at the moment. Step 1. http://tour.golang.org/ http://tour.golang.org/ Step 2. http://golang.org/ref/spec http://golang.org/ref/spec

elithrar 13y ago
Effective Go (http://golang.org/doc/effective_go.html http://golang.org/doc/effective_go.html) and Go by Example (https://gobyexample.com/ https://gobyexample.com/) are also great. The former is especially so if you want to learn Go idioms and understand why things are done. It's a good complement to the spec.
- MetaCosm 13y ago
  For some reason, I really enjoy showing this slideshow to people -> http://blog.menfin.info/Presentations/20120709_Golang_introduction http://blog.menfin.info/Presentations/20120709_Golang_introd... ... it is short, gets across a lot of the core ideas very quickly.
nknighthb 13y ago
Yes, please read the spec. All the specs! Shockingly few developers will read the f*cking spec for anything. It mystifies -- or perhaps terrifies -- me. It's one of the criteria I try to use to judge if I'm dealing with someone who seeks to truly solve problems, or just keep the build light from turning red. Some specs are actually kind of fun to read. POSIX is surprisingly pleasant, and sometimes amusing in a "Why is THAT warning label there?" kind of way. You don't have to treat them like a novel, but many are excellent reference material to keep at your fingertips.
- akama 13y ago
  You know the saying about warning labels. Ever warning label has a good story about why it came to be.

by staunch 13y ago

elithrar 13y ago

Effective Go (http://golang.org/doc/effective_go.html http://golang.org/doc/effective_go.html) and Go by Example (https://gobyexample.com/ https://gobyexample.com/) are also great. The former is especially so if you want to learn Go idioms and understand why things are done. It's a good complement to the spec.

MetaCosm 13y ago
For some reason, I really enjoy showing this slideshow to people -> http://blog.menfin.info/Presentations/20120709_Golang_introduction http://blog.menfin.info/Presentations/20120709_Golang_introd... ... it is short, gets across a lot of the core ideas very quickly.

nknighthb 13y ago

Yes, please read the spec. All the specs! Shockingly few developers will read the f*cking spec for anything. It mystifies -- or perhaps terrifies -- me. It's one of the criteria I try to use to judge if I'm dealing with someone who seeks to truly solve problems, or just keep the build light from turning red. Some specs are actually kind of fun to read. POSIX is surprisingly pleasant, and sometimes amusing in a "Why is THAT warning label there?" kind of way. You don't have to treat them like a novel, but many are excellent reference material to keep at your fingertips.

akama 13y ago
You know the saying about warning labels. Ever warning label has a good story about why it came to be.