For me, doing (in that order) the go tour [1], then reading "effective go" [2], then reading the language specs [3] have been a very good and immersive experien

For me, doing (in that order) the go tour [1], then reading "effective go" [2], then reading the language specs [3] have been a very good and immersive experience (of course, playing with some code along the way), better than a book. Bonus point: those are official docs, so you can expect them to keep up to date. Note: "language specs" may sound scary at first (it certainly scared me), especially if you have w3c specs in mind. But this is actually very different, specs are pleasant to read and somewhat look like a documentation (past the mandatory "how to read those specs" section and its arid specs content conventions explanation). [1] https://tour.golang.org/welcome/1 https://tour.golang.org/welcome/1 [2] https://golang.org/doc/effective_go.html https://golang.org/doc/effective_go.html [3] https://golang.org/ref/spec https://golang.org/ref/spec