About
A bit about me, and what I'm working on right now.
I'm a technology consultant based in the US. My background is in software engineering — I spent several years building production systems before shifting into consulting, where I now work with organizations navigating complex engineering decisions, mostly around AI and distributed systems.
The work is mostly about helping teams think clearly: scoping problems well, making architectural decisions that age well, and figuring out where new technology genuinely helps versus where it adds noise. I care a lot about writing and clear communication as a professional discipline — most engineering problems I've seen are fundamentally communication problems.
Outside of client work, I build things for myself — small tools, experiments, projects that scratch a personal itch. Some of them end up on subdomains here. I read a lot, mostly history, philosophy of mind, and technical writing.
This site is where I think out loud. Posts range from short observations to longer essays. Nothing is written for an audience in particular — if it's useful to someone, that's a bonus.
A personal reading tracker with structured notes. Trying to get the data model right before building the UI. Aiming for something that works like a commonplace book.
Three posts on how language models are changing the consulting workflow — what's actually useful, what's hype, and what I'm still figuring out.
Graeber and Wengrow's revisionist history of human social organization. Slow going but rewarding. Good antidote to Silicon Valley teleology.
What would it mean to treat LLM evals the same way we treat unit tests — fast, automated, part of CI? Working through whether the analogy holds.
Last updated May 2026 · /now page