About

I'm a frontend architect who cares more about the problem underneath the code than the code itself.

How I think about engineering

Code is a byproduct.

The primary deliverable is a solved business problem and a developer experience people don't have to fight.

Performance and accessibility aren't features.

They're baseline properties of anything I ship, not a backlog item for "later".

Boring technology, used well, beats clever technology used poorly.

I reach for the new and low-level (Zig, WASM, Workers) only once the boring option has been measured and found wanting.

Engineering impact

Frontend Lead, Dataddo

  • Led the migration from Vue 2 (Options API) to Vue 3 + Composition API and TypeScript across the core product, retiring an entire class of prop-typing bugs.
  • Rebuilt the marketing site from Nuxt 2 to Astro to hit sub-1s LCP and a clean 100/100 Core Web Vitals score, doubling organic search impressions within two quarters.
  • Mentored two engineers from their first commit to shipping independently at medior/lead level, building a repeatable onboarding and code-review process along the way.

Leadership & mentoring

I treat code review as a teaching surface, not a gate: every comment explains the why, not just the what. Mentoring works the same way I debug - find the actual constraint, not the symptom, and let people own the fix.

Currently exploring

Certified Senior Vue.js Developer - certificates.dev

ZigWebAssemblyWebGPU

Off the clock

When I'm not at the keyboard I'm usually pulling espresso shots, out for a run, or slowly losing an argument to my kid about bedtime. All three have taught me more about patience than any sprint retro.

Let's talk

Happy to talk architecture, the Vue ecosystem, or performance consulting.

vaclav@hrouda.dev