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

<p>Hey guys, I&#39;ve been writing Golang professionally for about three years now. I&#39;ve trained people and have worked from embedded Linux through to big scaled web systems and I get similar questions over and over:</p> <p>How should I write Golang? how do I lay it out to make <code>go get</code> work? What do I avoid? How do channels work etc? How go I use CGo to do X? </p> <p>I figured the official Go book would&#39;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&#39;ve been handled better and had you banging your head against the wall?</p> <hr/>**评论：**<br/><br/>shovelpost: <pre><p>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.</p></pre>DualRearWheels: <pre><p>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 $. </p> <p>Definitely wrong way to popularize own language.</p></pre>iends: <pre><p>I really want a good book on Go concurrency, and concurrency patterns. something along the the lines of Pike&#39;s &#39;Concurrency Is Not Parallelism&#39; but more depth.</p></pre>daveddev: <pre><p>Concurrency in Go &#34;Tools and Techniques for Developers&#34; By Katherine Cox-Buday</p> <p><a href="http://shop.oreilly.com/product/mobile/0636920046189.do" rel="nofollow">http://shop.oreilly.com/product/mobile/0636920046189.do</a></p> <p>I ran into Katherine&#39;s editor at my neighborhood market mid last year. I&#39;ve not preordered it yet, but there&#39;s a solid chance it&#39;s worth picking up.</p></pre>iends: <pre><p>Nice, looks solid.</p></pre>TheRealHellcat: <pre><p>I would like a solid article about best prectices, DOs and DONTs, how to layout the structure of the application.</p></pre>snake_case-kebab-cas: <pre><p>As someone mentioned, there are already quiiiite a few books.</p> <p>For example: <a href="https://www.packtpub.com/application-development/go-programming-blueprints" rel="nofollow">https://www.packtpub.com/application-development/go-programming-blueprints</a></p> <p>Obviously there&#39;s room for more/better all the time, but a thorough review of what&#39;s out there would be a good place to start!</p></pre>