I architect and ship web products that balance user experience with operational excellence. From domain modeling and API design to frontend delivery and observability,
I make sure each layer is predictable, resilient, and maintainable. I like turning ambiguous goals into clear plans and production-grade systems.
Work Experience
Sep 2018 - Present
Aug 2017 - Sep 2018
Jul 2015 - Aug 2017
Aug 2012 - Jul 2015
Latest Notes
Some of my recent thoughts
AI Won't Replace Developers-But It Will Expose the Gaps
Why AI coding assistants make good engineers faster and bad practices more dangerous.
Design Systems After Validation: Speed Without Chaos
Why early-stage startups should skip design systems-and why scaling products can't survive without them.
Define the Business Process Before Writing Code
Why startups that skip process documentation waste months on features no one uses-and how to prevent it.
Frequently Asked Questions
Common questions about my experience and how I work.
10+ years in web development. Started with WordPress and PHP integrations, went through the jQuery-to-React transition, and now work on enterprise-scale applications and AI/LLM products. I've led frontend architecture for a product suite with 50+ applications.
Design systems (70+ component UI kit with theming), complex frontends (dashboards, PDF builders, WYSIWYG editors), large-scale migrations (jQuery to Vue/React), build pipelines (3-4x faster with Vite), and AI-powered tools for content and brand monitoring.
Yes. As a Frontend Lead, I took on responsibilities typical of Staff Engineer and Engineering Manager roles — establishing coding standards, mentoring engineers at all levels, coordinating between design, product, and engineering teams, and defining technical strategy for a large codebase with 50+ applications.
Yes. I initiated and led the development of a design system from scratch — a UI kit with 70+ components, Storybook documentation, and a theming system based on design tokens. It runs in a monorepo with TypeScript, automated changelog generation, private package publishing, and developer notifications via conventional commits.
Yes. I've built production-ready boilerplates for rapid product development — monorepo setup with Nuxt, type-safe API clients, validation with Zod, and layered architecture that keeps the codebase clean as the product grows. The goal is fast iteration without accumulating tech debt from day one.