The person behind the code

A front-end engineer who cares about clarity, collaboration, and building things that quietly work well.

A little bit of history

I've been working in front-end development for over a decade. I started out in , then continued my career in the Netherlands, working across agencies, startups, and product teams. That gave me a good view of different ways software gets built — from quick early-stage work to more mature products where scale, maintainability, and teamwork matter a lot more.

Over the years I've worked on a wide range of products. Some were content-heavy, some were more service-oriented, and some were complex platforms with real user flows, account management, mobile apps, scheduling, or real-time interaction. That variety shaped the way I work now: practical, detail-oriented, and always aware that a product has to work well both for users and for the team building it.

  1. 2010 - It all started in Hungary

    This is where it started: small client work, websites, creative projects, and learning by doing. It taught me early that building software is also about trust, ownership, and making something useful for real people.

  2. 2013 - Learning speed in agency work

    My first proper agency years gave me repetition, pace, and a strong technical base. I learned how to turn ideas and designs into working products quickly, while still paying attention to structure and quality.

  3. 2015 - Getting closer to product development

    This was the point where the work started to feel less like "building pages" and more like building actual products. I got more involved in application thinking, front-end architecture, and the kind of decisions that affect how a product grows over time.

  4. 2016 - Moving to the Netherlands for a new chapter

    Relocating to the Netherlands was both a personal and professional step forward. It pushed me into new teams, new expectations, and a more international product environment where I kept growing as a developer.

  5. 2016–2022 - Agency work, SaaS, and product breadth

    These years gave me range. I worked across SaaS and agency environments, built web and mobile products, and learned how to adapt to very different domains without losing consistency in how I build.

  6. 2022 - Stepping into technical leadership

    By this point, I was not only focused on implementation anymore. I started taking more responsibility for front-end direction, team consistency, and the longer-term health of the codebase.

  7. 2023 - Product depth, full-stack thinking, and AI in practice

    My most recent chapter pulled several things together: product complexity, backend collaboration, automation, and AI as part of everyday engineering work. It felt like a more modern version of software development. Still grounded in fundamentals, but with better tools and a wider perspective.

  8. Today - Product-minded front-end engineering

    Today, I see myself as a front-end engineer with strong product instincts, a good eye for maintainable systems, and enough full-stack understanding to work across boundaries when needed. The common thread through all of it has been building digital products that are clear, useful, and well put together.

Technical focus

Most of my work has been centered around React, TypeScript, and modern front-end development. That's where I feel strongest. I like building interfaces that are easy to understand, easy to extend, and solid enough to support real product growth over time.

Depending on the project, that has also included Next.js, React Native, Node.js, NestJS, PostgreSQL, GraphQL, and other tools around product development. My main focus is still front-end, but I'm comfortable stepping into backend work when a feature needs it. I've found that understanding the full flow behind a product usually leads to better front-end decisions too.

React
TypeScript
Next.js
JavaScript
Node.js
NestJS
PostgreSQL
Tailwind CSS
GraphQL
Docker
Socket.io
Slack
Vite.js
Claude AI
React
TypeScript
Next.js
JavaScript
Node.js
NestJS
PostgreSQL
Tailwind CSS
GraphQL
Docker
Socket.io
Slack
Vite.js
Claude AI
StackShareExplore my full tech stack online

AI enters the conversation

AI has become part of how I work, but in a very practical way. I use it as support during development: exploring approaches, speeding up repetitive tasks, checking ideas, and helping move implementation forward faster when it makes sense.

What matters more to me than the tool itself is how it is used. I'm not interested in forcing AI into everything. I'm interested in using it well — in a way that reduces friction, improves workflow, and still keeps engineering judgment in the center of the work.

Explore

Research patterns, validate approaches, and understand trade-offs before writing code.

Implement

Build solutions faster with AI assistance while maintaining code quality and architecture.

Refine

Iterate on implementations, optimize performance, and polish the final product.

Product mindset

I've always liked the part of engineering that sits close to the product itself. A good solution is technically fine, needs to make sense for the user, fit the product, and be realistic for the team maintaining it.

That's one of the reasons I like front-end work so much. It's close to the experience people actually have, but it also touches structure, logic, and long-term decisions. I like that mix. It keeps the work grounded.

  • Simplified front-end structure to keep pages faster, lighter, and easier to interact with
  • Reduced unnecessary rendering and UI overhead in feature-heavy parts of products
  • Focused on implementation choices that improved responsiveness and perceived speed

Today

Right now, the things I care most about are front-end architecture, product-minded engineering, and practical AI-supported workflows. I like building things that are modern but not overdesigned, technically solid without becoming heavy, and useful in a way that lasts.

This portfolio is a place to show a bit more about that: the way I work, the tools I use, and the kind of products I enjoy building.

Front-end heavy

Building front-end structures for years. I keep things minimal, reusable, and maintainable while choosing the right tools for each challenge.

Product-minded

I only build products I believe in. After aligning on goals, I focus on clarity and consistent delivery that moves the needle.

AI support

AI is essential to modern development. It accelerates workflows, helps explore ideas, keeps documentation current, and makes daily development smoother.

Collaboration

Communication is key. I've worked across different team structures—from Kanban to Scrum and everything in between. I adapt quickly.

Let’s build something that lasts.

Have an idea, a product that needs fresh energy, or just want to exchange thoughts about React and architecture? My inbox is open. No bots. No auto-replies. Just a real conversation.

Start the conversation

© 2026. Created by me with ❤️