Development

I’m a designer who codes. I build what I design, so nothing gets lost between the mockup and the shipped product.

Why one person for both

Normally a feature goes from designer to spec to developer, and something always gets lost along the way. Animations feel off, edge cases get guessed, and everyone spends a week in Slack arguing about what the mockup meant.

When I do both, there’s no handoff. A lot of details are faster to build than to document, so I just build them. Fewer people, fewer meetings, faster shipping.

What I build

Front-end

My bread and butter. Vue, React, TypeScript, and CSS that your team can keep maintaining after I’m gone. Accessible, responsive, and fast.

Full products

I’ve built entire SaaS products by myself, back end included. Baseline runs on Django, Postgres, and AWS. Prose is a desktop app with its own AI gateway and usage-based billing. So if your project needs more than a front-end, I can cover that too.

AI features

LLM integration, streaming interfaces, prompt design, and the billing and infrastructure that come with it. I built all of that for Prose, and I use AI coding agents every day.

Working with your team

Jumping into an existing codebase is normal for me. I adapt to your stack, your workflow, and your deploy pipeline quickly, instead of making you adapt to mine.

Tech

I’ve worked in pretty much every common stack, so picking up yours won’t be an issue. Lately it’s mostly:

• Front-end: TypeScript, Vue, React, Next.js, Tailwind, Electron, Svelte
• Back-end: Node.js, Python, Django, PostgreSQL, PHP, Laravel
• Infrastructure: AWS, Docker, GitHub Actions

Ready to build?

Tell me what you’re working on and I’ll send a proposal within a couple of days.