npf.io

With AI writing a lot more of our code, we need to optimize for the human code reviewer.

Someone at work asked the following question: Why write code like this: foo := getFoo() bar, err := getBar() instead of this: var foo Type = getFoo() var err error var bar Type bar, err = getBar(foo) Isn’t the latter more explicit?

How to “do” enums is a common problem in Go, given that it doesn’t have “real” enums like other languages.

Error wrapping in go 1.13 solved a major problem gophers have struggled with since v1: how to add context to errors without obscuring the original error, so that code above could programmatically inspect the original error.

Pay remote workers the same as you’d pay local workers.

The proposal There’s a new Go proposal in town - try().

I have been working remotely for about 8 years now.

I was so happy when I discovered retool.

func init() in Go is a weird beast.

I’d like to announce starlight - https://github.com/starlight-go/starlight.

A Brief History A question came up at the Framingham Go meetup a while back about why something like Gradle hasn’t taken hold in the Go community.

There’s a new error handling design proposed here.

So, I don’t really like the contracts defined here.

There’s a disturbing thread that pops up every once in a while where People On The Internet say that comments are bad and the only reason you need them is because you and/or your code aren’t good enough.

If you tell the truth, you don’t have to remember anything.