Reading List
This page is auto-generated from Github Actions workflow that runs every day at night and fetches the 5 latest articles from each of my favorite blogs.
Yzma
In the previous article we looked at what inference actually is — how a model takes a prompt and builds a response one token at a time. I mentioned two Go projects that let you run that loop locally: yzma, which lets Go call the llama.cpp inference engine directly, and kronk,...
Some ways to navigate through 'git blame' over time in GNU Emacs
An interactive tour of Go 1.27
#613 — August 7, 2026 Read the Web Version Go Weekly An Interactive Tour of Go 1.27 — Anton Zhiyanov made interactive tours for Go 1.22 through 1.26 but decided to stop. Jesús Espino has picked up the baton and tackles Go 1.27's hu...
Looking at the memory map of a Go 1.27 program on Linux
Writing code isn't the bottleneck anymore, reading is
This week I was working on one non-critical feature that seemed simple at first sight. 50k lines of code later, it seemed to work as expected. In a side project, or a service where “nobody will be upset if it’s dead and kills everything around”, it would be read...
Code like a pirate with AI
Will AI coding agents pirate all our jobs? Not if we take back control, using my six-step PIRATE workflow for shipboard discipline.
Relative velocity and closing speed
In Physics simulations or game engines it’s sometimes useful to determine the speed with which two objects are approaching each other. This post will discuss the concept of closing speed, which is the normal component of the relative velocity of two objects. Relative velocity...
What '<code>sh -x</code>' mostly doesn't tell you about a shell script
Fake Clocks, Real Guarantees: Inside Go's synctest
The first time I reached for testing/synctest, I assumed it was a sleep helper with better manners. The public API is small enough to support that assumption: synctest.Test(t, func(t *testing.T) { ... }) synctest.Wait() synctest.Sleep(d) // new in Go 1.27 Three functions, one obv...