Background
I'm a backend engineer who cares about building systems that hold up: ones that stay correct under load, degrade gracefully when something breaks, and remain legible to the next engineer who has to work with them.
My instinct is always to understand the constraints before reaching for a solution. Good software engineering, to me, is mostly good reasoning about trade-offs.
How I Got Here
I fell into software through an obsession with how things work. Early on it was tinkering with scripts to automate tedious tasks. Slowly, that curiosity grew into a genuine passion for system design and backend architecture.
Over time I gravitated toward the parts of the stack most people don't see: API layers, data pipelines, the glue between services. That's where I find the interesting problems.
Current Focus
Right now I'm building Buck-et List Brands, a production-grade e-commerce platform for a niche hunting and outdoorsman apparel brand. It's a single Next.js 14 app on Vercel with Postgres on Neon (via Prisma), Stripe-hosted checkout scoped down to SAQ A, and Resend for transactional email. The stack was chosen so one developer can hold the whole system in their head while keeping fixed infra costs at zero.
The interesting work has been on the backend: faceted catalog filtering, a Stripe webhook that's the durable source of truth for the order state machine, an admin dashboard for inventory and fulfillment with full audit trails, and revenue analytics. Basically, the unglamorous plumbing that decides whether a store actually runs at scale.