ABOUT

How I approach systems: clarity, tradeoffs, and long-term maintainability.

THE BACKSTORY

workspace photo / headshot

I started building because I hated doing the same thing twice. Small scripts turned into a discipline — then a way of thinking. Every system I touch starts from the same question: can this run without me watching it?

I've worked across trading systems, agricultural ML, and Thai speech recognition — connected only by curiosity. I govern my AI collaboration with written rules: every decision becomes documentation, every output is auditable.

HOW I WORK

PLAN
Understand current state first
BUILD
Implement against approved spec
OBSERVE
Test assumptions against reality
ITERATE
Small, documented commits
DOCUMENT
Decisions + constraints

WHERE THIS IS GOING

Long-term, I'm building toward a personal toolbox — interconnected systems that handle the predictable parts of work and life. Every project I ship is a module in that larger system.

Right now, that means going deeper on system-design primitives and developer experience patterns. The goal isn't more tools — it's a stack where the right decision is also the easy one. Every project is a test of that.