Everything I have built.

2025

Give it a long video or recording and it writes out everything said, pulls out what matters, and hands you a report.

Role: Independent developer
The problem: Sitting through hours of recording to find the few minutes that matter is slow, and it is easy to miss something.
What I did: Built a pipeline: Whisper writes out the speech, Llama 3.3 reads the transcript and picks out the important parts, and the result is compiled into a PDF you can download and send on.

2025–

One place for tasks, journaling, scheduling and the numbers behind them, instead of four apps that ignore each other.

Role: Independent developer, ongoing
The problem: Tasks live in one app, notes in another, the calendar somewhere else. Nothing talks to anything, so you end up being the integration.
What I did: Each part is its own NestJS service with a clear boundary, so a change to journaling cannot quietly break scheduling. It is the architecture I would want to still be able to work on in two years.

2025

Turns rough notes into a finished, structured report: the repetitive part of writing one, handed off.

Role: Independent developer, active
The problem: Rewriting the same notes into the same report shape, every time, is work that does not need a person doing it.
What I did: A NestJS service takes the raw input, runs it through Llama 3.3 against a fixed report structure, and returns something ready to send rather than something you still have to edit.

2025

A shop demo with a working cart and a real Stripe checkout running in test mode.

Role: Demo build
The problem: Showing a client what an online shop feels like is easier than describing one.
What I did: Product listing, cart, and a Stripe Checkout session created by a small serverless function.

2025

An events site where a guest can request a table and the request arrives as an email.

Role: Demo build
The problem: Venues take bookings over the phone and lose them. A form that emails the request is enough to fix that.
What I did: Events listing plus a booking form backed by a serverless function that sends the request through Resend.

2025

A straightforward multi-page site for a small business: the kind most clients actually need.

Role: Demo build
The problem: Most small businesses need four good pages, not a platform.
What I did: Home, services, about and contact, built to load fast on a slow connection.

2025

A single-page product launch site, focused on one message and one action.

Role: Demo build
The problem: A launch page has one job: say the thing, then give people one button.
What I did: One page, one message, one call to action, and nothing else competing for attention.