LocationSt. Petersburg, FL
OPEN TOCONTRACT · CTH · FT
STATUSAVAILABLE
[01] Working with AI

Part of
the toolkit.

AI is integrated and leveraged in almost every aspect of my work now. I use Claude daily to assist with my development, the same way I lean on a framework, a library, or a good answer on Stack Overflow. It's one more tool that helps me get from an idea to something that runs.

It hasn't changed what I care about, which is shipping things that actually work. It's changed how fast I can get there.

The practical upside is that I can take on more as one person. Builds that used to need a small team are now something I can scope, prototype, and ship on my own.

Here's how that looks day to day, and where I don't hand things off.

Claude Code Claude API Prompt & spec design AI-assisted dev LLM / API integrations
[02] In practice

Day
to day.

Prototyping
Beforea weekend, maybe a small team
Nowidea → working build, same day
CircuitSync · SvelteKit + PocketBase
Understanding code
Beforean afternoon of guessing
Nowunfamiliar code mapped in minutes
WordPress plugins · Svelte stores I haven't touched in weeks
Debugging
Beforestaring at a stack trace
Nowdescribe → test → rule it out
the loop from broken to fixed got a lot shorter
The glue work
Beforemanual, repetitive plumbing
Nowscripts and wiring, handled
the Airtable + Zapier flows behind FourCorners onboarding
[03] The honest part

Where I
draw the line.

I don't hand off the thinking. AI is fast, but it doesn't know what's worth building, where the real risk is, or when it's confidently wrong. Those calls are mine.

So I read what it writes, I own the system end to end, and I stay responsible for the result. It speeds up the work. It doesn't replace the judgment behind it.

Selected Work Contact