Frontend developer — Barstow, CA
I came to software from construction and industrial automation, fields where you learn fast that every system has a root cause worth finding. Now I build React and Next.js products the same way: measured twice, deployed live.
Work orders
Every job below is deployed and live, not a tutorial, not a mockup. Open them. Break them if you can.
Founder / sole builder, decision archaeology for codebases
A Git history analysis tool that reads repositories instead of measuring them. It reconstructs the whybehind undocumented changes, tiered High / Medium / Low confidence findings, inference flags, and blast-radius scoping, so the first answer a new engineer gets isn't “ask whoever wrote it.”
Full-stack build, subscription book-summary platform
A complete Blinkist-class product: Firebase auth, Redux Toolkit state, Stripe subscriptions with tier detection, audio player, skeleton loading on every page. The whole revenue loop works — sign up, subscribe, consume content.
Solo build, codebase health diagnostics
Point it at a repository and it writes the chart: a diagnostic read of codebase health behind a GitHub OAuth gate, with hard cost controls, token caps and concurrency limits, because shipping an AI product means engineering the bill, too.
Unsolicited redesign, shipped before being asked
A speculative landing-page rebuild for a real startup, matching their brand voice their own website was missing. Built, deployed, and sent straight to the founder because showing value beats describing it.
Materials & methods
The same rule as the fabrication shop: know your materials, or they'll surprise you on install day.
Background
Before software, I built things you could stand on. Construction, tile and granite fabrication, industrial automation and maintenance, work where a measurement error doesn't throw a console warning, it costs material and time.
That background didn't get left behind; it became the method. I trace problems to root causes instead of patching symptoms. I check the wiring before blaming the component. I treat a messy commit history the way I'd treat an old job site as evidence of how the thing was really built.
Trained at FES Institute, now shipping production React with live users, live payments, and live consequences. Off the clock: composing in GarageBand, drawing pixel-art sprites for a Python space shooter, and riding motorcycles through the desert.