trace.
A tiny terminal tool that turns noisy stack traces into something you can actually read.
I'm Evan, a software engineer working on developer tools. This is where I think out loud about systems design, type systems, and the small details that make products feel right.
/ 01 — Journal
Every abstraction is a promise about what will never change. Most of them quietly break it.
Not a sync protocol. A decision about who owns the data when the network goes away.
A refactor that removed more than it added, and why the diff felt better than any feature shipped.
Most people never open the settings panel. The initial configuration is the product.
Innovation tokens are finite. Spend them where the product actually differs.
A weekend spent inside the checker, and three ideas I stole for my own error messages.
/ 02 — Index
A loose map of the notes above.
Boundaries, state, and the long-term cost of a shortcut.
14 notes 02Compilers, editors, CLIs, and the feel of a fast feedback loop.
11 notes 03Why the untouched settings panel matters more than the new feature.
9 notes 04Short observations from things I built, broke, and rebuilt.
14 notes/ 03 — Work
A tiny terminal tool that turns noisy stack traces into something you can actually read.
Schema-first local storage with sync that behaves the same offline as it does online.
An editor prototype exploring what compiler diagnostics could look like inline.
/ 04 — Stay in touch
One email when I publish something worth reading. No cadence promises, no noise, unsubscribe anytime.