is it empty?
no
keep going
drag to spin
I like to build an IUI
rather than just a UI
turbopuffer's logo scrambles into place on hover or touch. I reverse-engineered it from their production bundle, then rebuilt it with Claude Code: the word now converges onto wherever your pointer lands and trails precisely along its path as you move.
Three rounds of iteration on the interaction model. Shipped as a typed, working component — not a mockup.
view the React component repositoryThe hero geometry from Simply Curious. Two tetrahedra merge, resolve into a star, and spin.
Hidden-line occlusion and direct manipulation, drawn by hand in canvas. No 3D libraries.
visit Simply Curious
Brand mark for Simply Curious, a product I designed and built end to end.
Astro, Cloudflare Workers, D1 — logo to backend, one person.
visit Simply Curious
MaxCardPoints finds the best credit-card stack for your actual spending. The optimizer runs entirely client-side — no calculation ever leaves the browser — while a Cloudflare Worker and D1 database keep the card catalog current behind the scenes.
Astro, Cloudflare Workers, D1, Alpine.js. Installable as an offline-first PWA.
visit maxcardpoints.com
Nature's Answers for You gives a local wellness practitioner a calm, approachable home online. I translated her printed card into a warm, responsive one-page site that explains her services clearly and makes the next step simple.
Visual direction and responsive front-end build in HTML, CSS, and JavaScript.
visit naturesanswers4u.orgI've always been driven by curiosity.
Before software: high-energy particle physics, organic farming, CNC machining, then electrical work — then whatever the house needed next. A bathroom. A deck. A furnace two HVAC technicians had already given up on; I found what they missed. I've always been the type to take apart what's broken, see how it works, then fix it.
I'd been playing with web design that whole time — static sites, PWAs, drawing the logos and graphics myself, always my favorite part. With AI I can do far more of it, and I've come a long way in understanding not just how to use it but where its limits are. I'm still learning — about AI, and about the development process itself — so I can make that workflow correct, not just fast.
Same question every time. How does this actually work?
I design the surface and build what runs underneath it. As a solo dev I never really had a choice — not that I'd have it any other way. I want to understand the systems that make the software work.
Now the question points at getting a job. I've been a stay-at-home dad for the past few years, still working part-time as an electrician. My youngest is getting older, so it's time to think about full-time again. My boss would put me on full-time tomorrow, but I've enjoyed working with AI too much to make wiring the answer. As my older son put it: "You're the only one who actually enjoys work." He's watched me at it constantly these past few months — building, talking about it, losing whole days to it. The time just flies.
So here I am. Portfolio site, updated resume, looking for full-time work where I can build and understand the systems underneath.
I heard about turbopuffer on The Pragmatic Engineer — the team, the way you work — and thought it might be a fit. Then I saw the logo animation. I liked it, but I caught myself hovering over it wishing it responded to where my pointer actually was. So I built that. AI made it quick, but not one-shot; you have to iterate to get it where you want it. Then I packaged it as a React component and put it on GitHub, so it's yours if you want it.
I'd like to build things with you.
The work above is the evidence.
MT
curious, adaptable, self-taught, hands-on, thorough, still learning