5 ms·

I was expecting an empty page with a huge "don't" in it. But instead there was interview excerpts from Go developers and a ambiguous list of "best practices".It

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

Kiro 11y ago
> I was expecting an empty page with a huge "don't" in it. Why?
signa11 11y ago
> I just don't see what people think others would understand by teleologic statements like: "write Go the way it wants to be written" well, this is a very general advice, approx. implying : "don't force your previous language's world view while programming in Go". 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 'javaesque' go, you would be fighting against the language. however, embracing a 'goesque' worldview of composition+interfaces as primary vehicle for program design, would/should make the overall experience quite a pleasant one.
rakoo 11y ago
> I just don't see what people think others would understand by teleologic statements like: "write Go the way it wants to be written" To me it means "Read what the creators thought about when creating Go and how they view it, and do the same". But really that applies to any craft that exists: instead of trying to apply and adapt what you already know, clean your mind and start from scratch.
- lhc- 11y ago
  Wait, the advice is "ignore your past knowledge and experience and start from nothing" ? That strikes me as terrible advice.
  - signa11 11y ago
    > Wait, the advice is "ignore your past knowledge and experience and start from nothing" ? That strikes me as terrible advice. well, with knowledge i hope there is wisdom as well to apply it in a manner befitting the context.
  - rakoo 11y ago
    More like "Don't try to shoehorn your existing knowledge into that thing you are trying to learn and use; it may or may not fit but isn't supposed to". That absolutely doesn't prevent you to use your knowledge as stepping stones to understand the new thing.

Kiro 11y ago

> I was expecting an empty page with a huge "don't" in it. Why?

signa11 11y ago

> I just don't see what people think others would understand by teleologic statements like: "write Go the way it wants to be written" well, this is a very general advice, approx. implying : "don't force your previous language's world view while programming in Go". 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 'javaesque' go, you would be fighting against the language. however, embracing a 'goesque' worldview of composition+interfaces as primary vehicle for program design, would/should make the overall experience quite a pleasant one.

rakoo 11y ago

> I just don't see what people think others would understand by teleologic statements like: "write Go the way it wants to be written" To me it means "Read what the creators thought about when creating Go and how they view it, and do the same". But really that applies to any craft that exists: instead of trying to apply and adapt what you already know, clean your mind and start from scratch.

lhc- 11y ago
Wait, the advice is "ignore your past knowledge and experience and start from nothing" ? That strikes me as terrible advice.
- signa11 11y ago
  > Wait, the advice is "ignore your past knowledge and experience and start from nothing" ? That strikes me as terrible advice. well, with knowledge i hope there is wisdom as well to apply it in a manner befitting the context.
- rakoo 11y ago
  More like "Don't try to shoehorn your existing knowledge into that thing you are trying to learn and use; it may or may not fit but isn't supposed to". That absolutely doesn't prevent you to use your knowledge as stepping stones to understand the new thing.