Writing code for a living is a tricky business. There’s a lot that happens even before a line of code is put on the screen: meetings, gathering requirements, asking questions, discussions on which technology stack to use, and so on.

All of this is done with one purpose: figuring out the shape of the solution to the problem. We do this because, humans aren’t yet able to read each other’s minds. And because we need a proper understanding of the task at hand before we can start working on it.

…

Go uses channels as a means of communication between threads (goroutines).

Today I want to look how can we use channels sequentially, to pass information from one goroutine to another in a sequence, creating a sort of pipeline.

And for that we’re going to need some sugar.

…

Recently, I’ve been on a journey to learn Go.

One of its defining features, is the concept of Channels.

Channels are the way Go enables communication between asynchronous code, which in Go takes the name of goroutines.

…