Many-Step Sequences in Go
Breaking up programs with lots of linear steps.
The technical blog of Chris Lesiw, a Go developer with a focus on building simple, robust, and sustainable software.
Breaking up programs with lots of linear steps.
An overview of Go structs: fields, tags, empty structs, size optimization, anonymous declarations, and embedding.
I wrote a small program to answer the question, "Now where did I put that code?"
Deferring is a useful mechanism in most of Go, but in tests, there's a better way.
The golang-announce Google group wasn't available as an RSS feed, so I wrote a small program to fix that. Here's the feed if you'd also like to use it.
A collection of Go wisdom for easy access and sharing during code review.
A transcription of the Go Proverbs talk given by Rob Pike at Gopherfest 2015.
Want a codebase that's easier to read, maintain, and extend? Enforce a line length limit.
Go methods don't have to be declared on structs.
Go applications are very self-contained. So self-contained, in fact, that they can act as their own Docker container!
Go doesn't come with stacktraces. It encourages you to build your own.
Recommended git configurations and other tips.
The "functional options" pattern in Go is very silly. Here's an easier alternative.
If you need multiple goroutines to wait for the same thing, use a done channel.
What's the right way to handle errors in the main function?
Python has a handy for/else construction. Go has an equivalent.
This page collates some strategies I've found useful when testing Go programs.