Best Practices for Writing Clean Interfaces in Go (qvault.io)

If you use golang, I can’t recommend reading parts of the standard library enough. Make sure you can jump to source easily! This is true for many languages (less interpreted ones that are partly in C). Given how there are very few ways to do things in go, the libraries are very clear, concise, and performant. For interfaces I’d start at the io or http package.

This is a bit tangential, but it relates to the post: I'm currently working on a little side-project and I wanted to write (part of) it in Go. As a side-note, the last time I wrote Go was all the way back when I made a few small contributions to the language, circa 2009. As soon as I set up my environment, my gears were already turning (coming from Python, TypeScript, Java, etc.): how should I structure things? Where should this live? What should be calling what, and where should things be passed from and into?

And, like a breath of fresh air, I started remembering how Go works: it's a very simple, stupid language -- in the best possible way -- and it just works. You start writing code, and then you write more code. You write a function. And then you write another one. Slowly, your program gets bigger. Sometimes you need to split up functions.

And that's it. No fiddling with project structure, with taxonomies, and with hierarchies. I forgot what it felt like to just sit down and write some code. I've gotten used to battling tooling, fighting with opinionated frameworks, and having a zillion ways of doing something -- stuck in an eternal analysis paralysis.

I missed Go.

This elides the most important thing to understand about interfaces, which is that they should usually be defined by the code that consumes them, rather than by the code that provides things that implement them.