About
I've been a computer guy for as long as I can remember.
The engineering mindset came before anything I could put on a résumé. The route after that has been considerably less tidy.
Not in the neat retrospective sense where I was obviously destined to become a software engineer. I just always ended up around computers. I liked figuring out why something worked, why it didn't, what happened if I changed it, and eventually how to make something of my own.
My actual route here has been much less tidy. I don't have the conventional software career behind me. No long sequence of junior-to-mid-to-senior jobs. I've worked other jobs, including bartending during summers, but most of what I know technically came from years of already being at the computer, already curious, and increasingly capable of turning that curiosity into real systems.
Language and literature have been another long-running part of my life. I studied English Language and Literature, and somehow the two sides have never felt especially separate to me. I can spend one day thinking about binary protocols or agent infrastructure and another reverse-engineering sound changes, reading mythology, or obsessing over how ancient pottery could become the interface of a game.
Apparently my interests did not receive the memo that a personal brand should have one category.
I love the early part of making things: when there is still a problem to understand, when a vague idea starts acquiring structure, when several apparently unrelated pieces suddenly become one system. I am also very capable of taking a perfectly reasonable idea and discovering that it secretly requires an entire civilization of supporting infrastructure.
That part I'm working on.
ADHD is involved. So is being fairly introverted. Neither stops me from doing difficult work. Sometimes the exact opposite happens and I disappear into something for hours. The harder parts tend to be starting when the task doesn't catch properly, stopping when it catches too well, returning once I've lost the thread, finishing after the interesting questions are answered, and doing all the social work that makes something visible afterward.
For a long time I treated those as defects that had to be disciplined out of me. I'm trying something else now. I'd rather understand the machine I actually have and build around it.
I'm also trying to build a career rather late and somewhat sideways. I don't have much interest in pretending otherwise. I would eventually like most of my living to come from things I build and own. That could mean software products, games, open source, writing, consulting, or something I haven't thought of yet. I don't expect that transition to be cinematic. I expect a lot of small releases, failed experiments, awkward conversations about money, temporary compromises, and learning skills I've spent years avoiding.
This site is part of that. I've written and built an absurd amount of material that effectively vanished afterward into repositories, chats, social feeds, old documents, or my own head. I wanted somewhere to put it. Not just the successes. The abandoned things too. The weird experiments. The decisions I later changed my mind about. The things I am still embarrassingly unsure of.
So this is my corner of the internet. Have a look around. If you recognize something of yourself in any of it, say hello.
Say hello ↗