I build AI systems
that actually work.

I started as a writer. English, history, literature. I spent high school doing business and debate, but mostly I was writing: essays, poetry, fiction. That's how I learned to think: through words.

Then came computer science. Two and a half years of it in college. Data structures, algorithms, systems. I was good at it, but something was missing. Coding felt mechanical. I was implementing, not creating.

Then AI changed everything. Suddenly, writing code meant writing prose. Understanding systems meant understanding language. The skills I'd built as a writer became the skills that mattered most.

I design and build AI systems. Not just prompts: full architectures. Multi-agent coordination. Memory systems. Self-improving loops. The infrastructure that lets AI work together and get better over time.

I read research papers and implement them the same day. I test every major AI tool and model as they come out. I go to hackathons and build under pressure.

Most importantly, I ship. Three companies. Six hackathon wins. Open-source tools. Production systems. I don't just think about this stuff. I build it.

Most people try to make AI do what they want. I think that's backwards. AI has its own nature, its own strengths and patterns. The best systems don't fight that. They work with it.

I believe in emergence over explicit programming. In coordination over raw capability. In letting multiple agents work together rather than trying to build one perfect model. The complexity comes from composition, not from any single part.

I also believe that understanding AI is understanding language. The same skills that make good writing: precision, structure, knowing your audience, also make good AI systems. That's why I don't call myself an engineer anymore. I'm a writer who builds with code.

I did all of this without a safety net. No salary. No investors. No degree yet. Just work and curiosity and the conviction that this is the most important thing I could be doing.

I've led teams: UX researchers, designers, engineers, cofounders. I've made the hard calls and lived with the consequences. I've failed publicly, learned quickly, and kept going.

When I say I understand AI systems, I mean I've bet everything on that understanding. And so far, the evidence says I wasn't wrong.