Adding Version Information to Go Binaries

One of the things that I find really neat about Go, is the single-executable delivery model. For small projects, it’s as simple as dragging and dropping the built executable right where I need it. After some time, however, I might easily forget which…

Go is Good Enough

Go won’t win a competition in language design, but will reliably fulfill (most) of your needs.

Have you heard about the Pareto Principle? Also known as the 80⁄20 Rule, it states that for many aspects of life…

My Reasons to Consider Go Coming from Java

I hate listicles, and I am highly hoping that this doesn’t become one of them. Yet, I somehow felt the need to write down the reasons why I am giving Go a second (or maybe, third 🤔) chance. To the Java developers out there, searching for a new weapon of…

Fetch Random Unsplash Images in Your Go Apps

Perhaps not known to everybody, Unsplash, the free stock…

Simple Immutable Builders in Go, Using Value Receivers

Even in a simple language like Go, concurrently updating mutable state is like playing with fire. Take this piece of code, for example:

l := content.NewLoader() 
l.PageCount = 5 
c := l.Load(bytes)

A Simple Way to Keep a Go App Up and Running

Poor man’s Kubernetes

I am a lazy programmer, experimenting with new ideas all the time. For these, running and deploying tiny Go apps as single executables is the closest way to see something in action. Yet…

I actually agree with this. There have been a few occasions in my work, where I nudged people to write code that fails right away, rather than obfuscate the flow with passing errors backs, only to panic in the main goroutine.

In the Go community, there is some kind of paranoia around panicking, as if it’s the worst thing…