ABOUT · PERSON
The developer who thinks like a designer
Five years building for the web, with a growing obsession with 3D and motion — engineering precision paired with design intuition, aimed at sites that make visitors stop scrolling and start clicking.
Where it started
My background is in data engineering, not design school — years spent building pipelines where the only thing that mattered was whether the numbers at the end were actually right. That habit never left. When I moved into building for the web, it came with me: measure outcomes, not just how something looks.
The move into web development came from a growing obsession with 3D and motion — seeing what a browser tab could actually feel like when nobody put a ceiling on the interaction design. That obsession is still the reason I build the way I do now.
How I think about design
Design and engineering aren't two separate phases of a project for me — they happen at the same time, in the same file. I design directly in the browser rather than handing off static mockups, because a layout that looks right in a design tool can still feel wrong the moment it actually moves.
Every pixel is intentional and every line of code earns its place. Zero templates, zero page builders — every project starts from a blank file, which is slower up front and faster to get exactly right.
What I actually measure
A data engineering background makes it hard to accept "it looks nice" as the final verdict on a website. The real questions are quantifiable: what does the Lighthouse score say, how fast does it load on a real connection, does the structured data actually validate, does the conversion path make sense to someone who's never seen the site before.
That's the throughline across every project in the portfolio and every page in the journal— the visual layer gets the attention it deserves, but it's never allowed to be the only thing that got attention.