Engineering

The story of how backlog-mcp grew from a task manager into local-first context and memory infrastructure for AI agents — and produced the UI framework powering this blog.

I am building ghx, a code reconnaissance CLI for AI agents, and now an agent sidecar framework around it. The hard question is whether any of it actually improves signal per token compared to plain old gh.

SA_ONSTACK is process-wide. sigaltstack is per-thread. When Go, Bun, .NET, and the JVM share a process, signals land on the wrong stack. One kernel field fixes the class.

Codemap, Aider, Gitingest, Repomix, and ghx solve different parts of agent code context: mapping, searching, packing, and deciding what to read before cloning.

On Kat Zhang's obsidian note network, the GitHub ecosystem around it, and what graph neuroscience says about the shape of minds

A CLI tool that looks simple took 23 agent sessions, 2,500+ turns, and three rewrites. This is what building with AI actually looks like.

Software engineering isn't going away — writing code without agents is. The role is expanding, not shrinking. Here's what that actually means.