I started as a Graphic Designer, worked as an Art Director, and found a passion writing code. That path wasn't a pivot — it was an accumulation. The design background shaped how I think about interfaces, systems, and communication. The art direction experience taught me how to manage complex projects, balance priorities, and make decisions that hold together across time and scale.
I'm a Front End Developer at heart, but one who works across the entire product lifecycle — from technical architecture and backend systems to front-end implementation and visual identity. Most projects are led entirely by me, coordinating design, technical, and infrastructure decisions from start to finish.
My work spans e-commerce platforms, SaaS tools, membership systems, learning applications, and more — but what connects them isn't the category, it's the approach. I like to work on problems that need a specific solution, and I enjoy building exactly that.
A pattern that comes up often is the custom tool. While building a platform, there's frequently a gap
— something a project needs that no library handles well enough, or at all. When that happens I build it:
an SVG parsing engine, a GraphQL-driven workflow system, an SRS algorithm, an audio processing pipeline.
Most of them ended up as open-source libraries, still in use and maintained today.
Open source matters to me beyond the pragmatic. I found something real in that exchange — sharing what I build, learning from what others share, collaborating without borders. Releasing a library means getting feedback from people using it in ways I didn't foresee, which makes the tool better and pushes my own thinking further.
The other thread running through most of my work is the intersection of engineering and design. Several projects here involved not just building the platform but defining the visual identity from scratch — logo, typography, color system, UI language — and then carrying that identity into the product itself. Having both perspectives is an advantage: it lets me design knowing what's feasible and code knowing what matters visually.