Background
I'm a web developer 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 developer 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 grew into a genuine interest in how whole systems fit together.
That curiosity turned into my first real job as a developer at Hounder, building client sites for counties, airports, and utilities. Working on software that people depend on to get something done has taught me more than any side project could: the constraints are real, the users are everyone, and the site has to still make sense to whoever maintains it next.
Current Focus
Right now I'm at Hounder, building client sites in Drupal, WordPress, and Laravel across the full production lifecycle: custom components and page templates, PHP and server-side logic, responsive CSS, content migrations, and accessibility audits. The clients are public agencies, so the QA bar is high and the browser matrix is wide.
Most of what I'm learning is the part that doesn't show up in a tutorial: how to structure a build so a non-technical editor can maintain it for years, how to keep configuration reviewable instead of clicked into a live admin UI, and how to reproduce a production problem locally before trying to fix it.