&gt; 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;<p>well, this is a <i>very</i> general advice, approx. implying : &quot;don&#x27;t force your previous language&#x27;s world view while programming in Go&quot;.<p>f.e. if you are coming to Go from say Java, where everything is a class and where hierarchies abound, when you try to write a &#x27;javaesque&#x27; go, you would be fighting against the language.<p>however, embracing a &#x27;goesque&#x27; worldview of composition+interfaces as primary vehicle for program design, would&#x2F;should make the overall experience quite a pleasant one.