About
I don’t have a clean answer to who I am.
That’s not deflection. It’s the most honest thing I can say — and I’ve learned to treat that honesty as a compass rather than a problem to fix.
I am technically inclined, but the technical part was never the point. When I build something — a custom shader, a CLI tool, a WebGL scene with geometric distortion — I’m not chasing functionality. I’m chasing rightness. The feeling when a system does exactly what it should, in exactly the way it should, with nothing wasted. That feeling is closer to aesthetic than engineering. I just happen to speak it in code.
I read obsessively. Fantasy, mostly — but not for escape. Malazan. Robin Hobb. Dostoevsky. Discworld. Long books with moral weight. Books that refuse easy resolution. I am drawn to characters who carry quiet storms — introspective minds, loner archetypes, people who understand more than they say and feel more than they show. I recognize something in them I don’t always have words for.
I oscillate between building structured systems and asking unstructured questions. Between technical precision and existential curiosity. Between designing something beautiful and wondering why beauty matters. Most people would call this fragmentation. I’ve come to think it’s the opposite — it’s what happens when you take everything seriously and refuse to rank your interests into a hierarchy that makes you legible to others.
What I Actually Care About
Craft. Not as a professional value. As a personal one. The difference between something that works and something that is well-made is invisible to most people. That invisibility is exactly why it matters to me.
Depth. I would rather understand one thing completely than skim ten things superficially. This applies to software. To books. To people. To myself.
Precision. Not perfectionism — precision. Knowing exactly what something is, what it does, and what it costs. Fluff is not neutral. It is a form of dishonesty.
The serious question. Not who am I as a crisis — but as a practice. A thing I return to. Most people answer it once and stop. I’m not interested in stopping.
What This Site Is
This is not a content strategy. It is not a portfolio. It is a working document from someone in the middle of a long, unfinished project — the project of building a coherent internal system out of things most people keep siloed.
Expect writing on systems architecture, software craft, books worth reading slowly, and the occasional attempt to think clearly about something that resists clarity.
I write here to think. Not to be read. The distinction matters — though you’re welcome to read anyway.
Find me on X