01
Occam's Razor
Solve one problem completely before adding the next. The simplest solution that ships beats the ambitious one that crashes.
§ 02
Story
I started building AI tools in July 2025. From day one I shipped in public against external deadlines. Seventeen hackathons in nine months. Five wins. Multiple ecosystems learned in real time.
The work is not weekend tutorials. It is deployed products solving problems: developer growth tracked from code, reasoning preserved across fast moving AI builds, agent readiness scanning for the web's next audience, IT support transparency for people who deserve to know what is happening with their tickets.
Most of the work shares a structural move: it takes something invisible and makes it inspectable. Code growth that was hard to measure. Reasoning that disappeared between sessions. Court systems that are hard to navigate. Web pages that AI agents struggle to parse. The work is in that gap. Findings, not fixes. The data speaks. The reader decides.
I do not write code from scratch. I provide creative direction and validation. I work with AI tools, compare their outputs, pick what works, and stitch them together into something that holds up. The AI generates. I direct. The output is mine. That is a deliberate workflow, not a limitation.
Every tool I build does the same structural thing.
It helps a system explain itself to the people who use it.
