I'd like to write a book... help?

Hey guys, I've been writing Golang professionally for about three years now. I've trained people and have worked from embedded Linux through to big scaled web systems and I get similar questions over and over:

How should I write Golang? how do I lay it out to make go get work? What do I avoid? How do channels work etc? How go I use CGo to do X?

I figured the official Go book would've been enough but the questions still come so I wonder - what is missing from the official docs, what did you struggle with that could've been handled better and had you banging your head against the wall?

---

评论：

shovelpost:

If experienced gophers stopped writing books and instead contributed to improve the official docs we would now have the best docs in the programming universe.

DualRearWheels:

Something reminds me of D. Bad on line docs since last decade, very frustrating to newcomers. But then a big shot (one of main devs) wrote a book on how to use it, so people could finally learn it if they cash out some $. 

Definitely wrong way to popularize own language.

iends:

I really want a good book on Go concurrency, and concurrency patterns. something along the the lines of Pike's 'Concurrency Is Not Parallelism' but more depth.

daveddev:

Concurrency in Go
"Tools and Techniques for Developers"
By Katherine Cox-Buday

http://shop.oreilly.com/product/mobile/0636920046189.do

I ran into Katherine's editor at my neighborhood market mid last year. I've not preordered it yet, but there's a solid chance it's worth picking up.

iends:

Nice, looks solid.

TheRealHellcat:

I would like a solid article about best prectices, DOs and DONTs, how to layout the structure of the application.

snake_case-kebab-cas:

As someone mentioned, there are already quiiiite a few books.

For example: https://www.packtpub.com/application-development/go-programming-blueprints

Obviously there's room for more/better all the time, but a thorough review of what's out there would be a good place to start!