Running
Main upcoming event.


BACKEND ENGINEER — GO
I've been writing Go since 2022, mostly on systems that aren't allowed to fall over. Away from the editor I train, work on my English, watch far too many films, and follow what happens around software as closely as the code itself.
ABOUT
I’m a Go developer. I build distributed backends — Kubernetes, Kafka and RabbitMQ, PostgreSQL, S3 — mostly on systems with a high SLA, where downtime is something that gets counted and explained. Outside of work I keep a steady queue of my own projects.
Before that I led the messaging and notification domain at a marketing platform delivering to tens of millions of recipients a day, and I started out doing computer-vision R&D in Python and C++.
From my perspective, there’s no decision that’s simply correct. Every choice buys something and costs something, and most of life is deciding which cost is acceptable this time.
So this is where I write about whatever I’m actually thinking about — technical or not.
NOTES
Two halves of the same notebook. Filter by what you came for.
If I had a son picking a university, here's what I'd point him toward — jobs AI will barely shift.
For the last three years, I've been tracking my income and expenses month by month
My watch under-measured the distance and accidentally taught me something engineers already have a name for.
You compare your whole life with someone else's best thirty seconds.
A Black Mirror episode about a subscription, and why it felt uncomfortably close to my own bills.
Not about pace or calories — about the moment your brain tells you to stop and you don't.
Three tiers of learning, and why the amount of content you consume is the wrong thing to measure.
A memory problem in a Go + cgo + GStreamer pipeline, and a fix that consisted of not having the pipeline.
Debugging used to end in a particular kind of joy. Lately it ends in a prompt.
Two things people underestimate at the same time — and what the income distribution looks like when you put them side by side.
Millions of people now ask the same systems the same questions — and get remarkably similar answers.
The Dunning–Kruger effect, and the question of which direction AI actually pushes people.
Nothing here yet.
OFF THE CLOCK
Main upcoming event.

Two or three a week. I keep a short list of the ones I rewatch, and occasionally that list turns into a note here.