Computer Broscience

The third post in the Foilworks series, and the one with no code in it. What a wing section is actually for, why there is no such thing as a good aerofoil, and the single budget that every trade in the field is paid out of.

The second post in the series. The other half of aerodynamics — a film about one percent of the chord thick in which all of a wing's drag and all of its stall behaviour are decided. Two numbers stand in for the whole velocity profile, one ratio decides everything, and the two solvers each need the other's answer before either can start.

Can you build a network that behaves like shared memory, with no token, no payment and no accounting of who stores what? I tried in Go two years ago. It worked, and then answering one much smaller question destroyed it. What actually failed, checked against the code — and the three answers the project has produced since.

Soaring Spirit is my first company, a Swiss GmbH running speedflying trips and coaching. The whole product runs as one Go binary on a Raspberry Pi in my house. Sixteen months in, this is what that choice has cost and what it has bought.

The first in a series about aerofoil design, written while building a simulation backend called Foilworks. Air behaves in two completely different ways depending on how close to the wing you are, and nearly every practical tool in the field is built on that split. This is the half with no friction in it — where lift comes from, and why the hardest part is a single missing equation.

As a way for me to dive deeper into Zig, I'm writing a HTTP server from scratch. This article describes some of the work I've done recently, and a few lessons that I've learned.

As a way for me to dive deeper into Zig, I'm writing a HTTP server from scratch.

I describe what I like about the Zig systems programming language, and what I don't like after a couple of weeks of tinkering.

Distributed KV store.

Real-time log tailing over UDP: a map of ring buffers, a protocol that ended up in production, and three wrong answers to replay protection before WireGuard showed me the right one.

I wanted to put a 4K video on Arweave. The web wallet burned my AR without telling me, ArDrive insisted on bundling, so I wrote the uploader — and then made it resumable.