Expertise
Go developer — services and tools that ask for no installation
When I need a service or a tool that asks for no installation on the other side and stays up for a long time, Go is where I reach first — not as an alternative to another language but as the answer to a class of problem.
- years
- 7
Me in the Go ecosystem
Writing a service or a tool is half the job; without cross-compilation, version embedding, signed output and an install path, what I wrote runs only on my machine. In Go work I build that second half too: microservices, consumers that take work off a queue without stopping, HTTP APIs and command-line tools shipped as a single file.
I do not bring in a package for work the standard library already solves; every dependency is a surface someone else will have to look after. Go work tends to outlive the day it was written, and it is not only the language that makes that possible but the short dependency list.
I pick the language by the problem, not because I like it. For the architecture side of these services, see the Software Architecture page. Not every job is a Go job; system design itself I write about, with its costs, in the Engineering section.
What is Go?
Go is a fast, statically typed, compiled language; go build compiles a program into an executable file. A Go developer writes services, queue-consuming processes and command-line tools in it.
What do I do with Go?
In Go I write microservices, consumers and workers that take work off queues, HTTP APIs and command-line tools.
Recent writing in this area
- Blog
The Silent Failure Is the Most Dangerous One: Fail-Closed in CommitBrief
On a partial config, one CommitBrief command silently turned off secret scanning. Silent failures I closed July to October, and the rule: fail closed.
- Blog
Same bug, different title: giving an LLM finding an identity
In CommitBrief, what counts as the 'same' finding moved from the title to a rule ID; baseline, policy and PR threads were built on that decision.
- Blog
Which model reviews better? I finally measured it
I measured CommitBrief's default models for the first time: Gemini cleared the threshold, while the OpenAI default raised too many false alarms.
Measurements in this area
64 goroutines on four cores: Mutex is 1.40 times faster than a one-way channel, but its p99 is four times higher
When G goroutines on P cores hammer the same shared counter, how many operations a second do sync.Mutex, an owner-goroutine channel and a buffered channel manage, and how do tail latency and fairness of waiting change?
Finding
With 64 goroutines on four cores, sync.Mutex is 1.40 times faster than a one-way channel (10.46 and 7.47 million operations/s) but its p99 wait is 4.00 times higher (294,911 and 73,727 ns). On eight cores the Mutex ranges from 16.27 to 26.25 million operations/s across the two runs (a bimodal cell); the one-way channel holds at 7.31 and 7.32 million. More than half of the cells are flagged in both runs; confidence is low.
measured 30 days ago
Technologies I pair it with
-
Cobra
Command tree and flag surface.
-
go-git
Commit-based operations; I fall back to the git binary when the working tree is involved.
-
Goreleaser
Cross-compilation, signed binaries and Homebrew/Scoop distribution.
-
Gin
The router I reach for once an HTTP service outgrows the standard library.
-
Fiber
The same job, in a shape familiar to anyone coming from Express.
Questions in this area
Frequently asked
9 questions
-
How long have you used Go?
Since 2019, so 7 years. All of it alongside PHP: Go never replaced a language for me, it stands as the answer to one class of problem.
-
Why did you learn Go?
Being polyglot was never the goal; I simply did not have the right answer for a particular class of problem. Go is statically typed, it compiles, its standard library is broad and its syntax is deliberately plain. I never intended to swap PHP out for it — my depth stayed there, and Go came to represent breadth.
-
What do the things you write in Go have in common?
Each is a process with one job that stays up for a long time and uses resources cheaply. That is also why it matters that they can ship as a single file that asks for no installation on the other side.
-
Do you write web services, or only CLIs?
Both. For HTTP I start with the standard library; `net/http` is usually enough to put an API into production. Gin or Fiber comes in when I need a middleware chain, route grouping or ready-made binding.
-
How do you switch between Go and PHP?
It has a cost, and I wrote it down: the real price of a polyglot codebase is not learning a language, it is switching context. On days when both are open at once, my error rate goes up.
-
What does a Go developer do?
A Go developer writes services, background workers and command-line tools. For me that means programs shipped as a single file, processes that consume from queues without stopping, HTTP APIs that feed web and mobile — and building the delivery path for all of them.
-
When do you pick Go for a job?
For four reasons: go build produces a single executable, the same source builds for Linux, macOS and Windows, concurrency (goroutines and channels) is part of the language, and plain syntax with explicit error handling makes life easier for whoever reads the code six months later. For a product that needs heavy business rules, a mature admin panel or a wide package ecosystem, PHP and Laravel still get there faster.
-
How do you design command-line tools?
The person using a tool is rarely the person who wrote it. So a command's name says what it does, the same flag means the same thing in every command, and an error message says not what went wrong but what the user should do next.
-
How do you relate Go to architecture decisions?
The delivery and redelivery behaviour of a service that takes work off a queue is an architecture decision before it is a language decision. Go is one of the languages I write those services in; how I make the decision is on the [Software Architecture page](/expertise/architecture/).
Let us work together
If you have work in this ecosystem, tell me what you are building and we will talk about how to build it.