Skip to content

Full-stack developer · Fox Valley, Wisconsin

I build complete products, and I build them fast.

Front end, database, admin interface, deployment, DNS. Most projects stall in the gaps between specialists — those gaps aren't there when one person carries the whole thing. By day I build the internal software platform of a manufacturing company — 15+ production apps and the infrastructure they run on — so I also know what the software is actually for once it reaches the floor.

How I work

Full products, not fragments
Front end, database schema, admin interface, auth, deployment, DNS. Projects usually stall in the gaps between specialists — those gaps aren't there when one person carries the whole thing.
Speed from AI, not corner-cutting
AI-assisted development has genuinely collapsed the mechanical part of building software. What it hasn't collapsed is deciding what to build, modelling it correctly, and verifying every layer of what comes back — which is where five years of shipping end-to-end without AI turns out to matter. A specialist can direct AI in one layer. I can direct and verify it in all of them.
I build manufacturing software
My day job is building a manufacturing company's internal software platform — 15+ production applications and the self-hosted infrastructure under them. I know what a changeover costs, why the schedule lives in a spreadsheet, and why the gap between what a system reports and what's actually on the floor is where the money goes. That context is unusual in someone who also writes the code.
Boring where it counts
Constraints in the database. Fail closed at trust boundaries. Static files where nothing needs a server. No dependency for something a few lines can do. The interesting decisions are worth agonising over; the infrastructure should be dull.

Got something that needs building?

Tell me what it is and when you're free. If it isn't worth building, or you'd be better off buying something off the shelf, I'll say so.

Get in touch

devonthibodeau@gmail.com