I built my first website in 1998. Since then I've worked across the full arc of web development: table layouts, Flash, PHP, the mobile web and jQuery, Node.js, JAMStack, React, and now Next.js since 2018.
Somewhere in between I studied Media Economics and Marketing, which turned out to shape how I think about code more than any programming book. It gave me a bias: I understand that code has to serve business goals. A technical improvement might change how users behave and hence increases the conversion rate. If the team can ship faster, it's a win for the whole company.
Today I specialize in Next.js performance and architecture. Most of my work is with scale-ups where the same pattern keeps showing up: smart developers, good intentions, but they're fighting their own infrastructure. Deploys that take 20 minutes, self-managed Kubernetes that blocks modern workflows, caching strategies that nobody on the team fully understands.
Slow developer experience kills momentum.
That's the problem I work on.
What I do
- Next.js performance optimization & caching strategies
- Clean architecture that scales without over-engineering
- Developer experience improvements: fast builds, smooth workflows, modern tooling
- Modern Next.js and React patterns
What drives me crazy
- Teams spending hours per day waiting on slow CI/CD pipelines
- Self-managed infrastructure blocking modern deployment workflows
- Next.js caching strategies that nobody explained properly (one of the most powerful and most misunderstood parts of the framework)
- Multi-repo setups when a monorepo would eliminate 90% of the coordination overhead
- Meetings that could have been an async update