Being riclib

In which a developer roasts himself with affection, and the conviction that self-awareness is the best debugging tool.

The Five Layers

The Five Layers

What a Programming Language Is When the Machine Writes Most of It An AI wrote four thousand lines of code yesterday. I wrote about twenty words. The code shipped. The reason it shipped is that...

Read essay |
Gall's Law Got Cheap

Gall's Law Got Cheap

Six weeks ago I wrote [[The Best Architecture Is the One You Delete]] about a sibling law called [[Liberato's Law]] — the reverse corollary that says the simple system replacing N complex ones...

Read essay |
Give Them Their Own Computer

Give Them Their Own Computer

Every week I see a new tool on X that puts a UI around multi-agent coordination. Worktree managers. Branch orchestrators. Agent spawners with dynamic allocation. Merge conflict dashboards. Each one...

Read essay |
The Eternal Search for the Perfect PKM App

The Eternal Search for the Perfect PKM App

I have been looking for the perfect note-taking app for sixteen years. I can now tell you with certainty that it doesn't exist, that I've tried all of them, and that the answer was a folder of text...

Read essay |
Why I Vibe in Go, Not Rust or Python

Why I Vibe in Go, Not Rust or Python

Conditional up front: this essay is about Go vs Rust vs Python for AI-assisted development with high machine-write percentage. It is not about Rust-for-humans, where Rust may well be the better...

Read essay |
The Rewrite Trap

The Rewrite Trap

The software industry has a dirty secret: it rewrites everything every twelve years, learns nothing from the rewrite, and does it again. I've watched this cycle from three angles — as a developer,...

Read essay |
The Best Architecture Is the One You Delete

The Best Architecture Is the One You Delete

Last week I replaced five systems with one. A NATS KV draft store. A pub/sub bridge. An event publisher. A streaming buffer. A render handler. Each correct. Each solving a real problem. Each doing...

Read essay |
Software Dies of Obesity, Not Starvation

Software Dies of Obesity, Not Starvation

Nobody ever killed a software system by not adding enough features. Every software system that has ever died — been replaced, rewritten, abandoned, or quietly moved to a server that nobody monitors...

Read essay |
0:00
0:00