I was expecting an empty page with a huge &quot;don&#x27;t&quot; in it. But instead there was interview excerpts from Go developers and a ambiguous list of &quot;best practices&quot;.It would be more meaningful if this was backed with some actual practices with some code examples.<p>I just don&#x27;t see what people think others would understand by teleologic statements like: &quot;write Go the way it wants to be written&quot;