Production React and Next.js development
Features and whole modules in large codebases, with TypeScript and tests as the default.
Nine years on production React applications — from enterprise platforms with 30+ engineers to products I built from scratch on my own. I get up to speed in a large existing system fast, and I use AI as a serious engineering tool, not a code generator.
Features and whole modules in large codebases, with TypeScript and tests as the default.
Application structure, state management, module boundaries and decisions that don't backfire six months later.
Gradually moving old code toward a maintainable state, without stopping delivery.
Measuring, profiling and concrete changes — not guessing what's slow.
Unit and integration tests, review culture and technical documentation that keeps up with the code.
Rolling structured AI workflows out to a team — repository context, review, tests, documentation.
Three things, clearly separated.
React and Next.js applications designed for production — not a demo that falls apart when real traffic arrives.
Architecture, performance, refactoring and legacy modernization — without rewriting everything from scratch.
Structured AI workflows for faster development without sacrificing code quality.
Two projects that best show how I work.
Personal trainers run their clients across three or four separate tools — training in one spreadsheet, nutrition in another, progress in a phone message. Nothing is connected, and the client has no single place to see their plan.
A SaaS platform combining client management, training programs, nutrition and progress tracking in one product — with separate workflows for the trainer and the client.
Product design · Frontend · Backend · Architecture · AI-assisted development
Outcome A complete product built and shipped solo — from database architecture to the mobile app.
A large legacy React codebase, a team of 30+ engineers and many repetitive development steps. Every task required significant context before the first line of code, while review and documentation constantly lagged behind.
Structured AI workflows around repository context, task-specific instructions, code review, test generation and technical documentation — AI as part of the engineering process, not a code generator.
Workflow design · Team rollout · Frontend development
Outcome ~30% reduction in development time on selected workflows, across a team of 30+ engineers.
AI isn't a replacement for engineering — it's part of my engineering workflow.
What I build products with every day.
Nine years shipping products in production.
Looking for a website or online store for your business? See services →
Got a project or an idea? Drop me a line — I reply fast.