Live data from Hacker News

I completed Ultimate Go, took good notes and commented directly on source code

github.com

11–20 of 53 posts

Re: I completed Ultimate Go, took good notes and commented directly on source code

#14
post #13

The design guidelines ( https://github.com/ardanlabs/gotraining/blob/master/topics/g... ) are especially good. And it's not go-specific, it can be applied to any software crafting tool.

Agree! I also included that in my note.

Re: I completed Ultimate Go, took good notes and commented directly on source code

#16
post #13

The design guidelines ( https://github.com/ardanlabs/gotraining/blob/master/topics/g... ) are especially good. And it's not go-specific, it can be applied to any software crafting tool.

[deleted]

I read that differently in light of the section heading "These Days Are Gone".

Re: I completed Ultimate Go, took good notes and commented directly on source code

#17

Earlier quoted context omitted.

[deleted]

I read that differently in light of the section heading "These Days Are Gone".

No this is not a section heading. This is a statement referring to what's before it.

We cannot "throw more developpers at the problem".

First because they are expensive. But also because that makes management exponentially expensive while necessarily helping with delivery (lump of work fallacy).

Or you are correct and this is appallingly bad drafting and formatting.

Re: I completed Ultimate Go, took good notes and commented directly on source code

#20
Great intro into how to write nice Go code! One comment regarding interface pollution: While I agree that in many cases it's not needed to introduce an interface, sometimes interfaces help you hide the implementor type: I've now already had it multiple times that I switched from a 'struct implementor' to a 'func type implementor' without breaking compatabilities. Also, by exposing a struct, you also immediately expose that you can create a zero value of that type, which doesn't happen for an interface.
Post reply on HN