About
I’m a web developer with an art director’s eye, a systems brain, and a healthy suspicion of “temporary” fixes that become permanent.
How I work
I build polished, responsive websites while paying close attention to the systems beneath them: reusable patterns, content structure, accessibility, performance, and the people who will maintain the work after launch.
Some projects begin with a detailed design. Others arrive as an aging website, incomplete reference material, or a codebase full of accumulated compromises. I’m comfortable identifying the underlying intent, deciding what should be preserved, and rebuilding the rest into something more coherent.
I work iteratively—establishing the visual language, testing it against real content and smaller screens, and refining the system when repetition reveals a better pattern. I document the decisions that matter so the next person can understand not only what the code does, but why it works that way.
What I bring to a build
I can interpret a design, identify its underlying rules, and carry them consistently across pages and breakpoints.
I look for repeatable patterns, weak assumptions, and places where a one-off solution will become tomorrow’s maintenance problem.
I give clear direction, respond well to feedback, and explain technical decisions without turning every conversation into an engineering lecture.
Responsive behavior, accessibility, content details, and QA are part of the build—not optional polish applied at the end.
Tools and process
I use the tools that suit the work, including WordPress, custom frontend systems, and AI-assisted development workflows. Automation can accelerate implementation and analysis, but I remain responsible for the architecture, visual direction, review, debugging, and final quality of what ships.
Need a polished frontend, a more maintainable system, or a calm hand inside a messy build? Let’s talk about what the project needs.
Start a conversation