I question before I build.
Before adopting a solution, I check whether it really fits the problem. That's how I came to shape 110+ UI building blocks of an in-house library that replaces a third-party framework – leaner and faster.

A software engineer who builds deliberately.
I build things that make people's lives easier – and in a way a team can build on: considered, lean, documented. I use frameworks and AI as a deliberate choice, not out of habit.
About me
Software engineer – currently working mainly in frontend, but not defined by it. I build software that makes people's lives easier, and I keep mature e-commerce systems running and evolving. I deliberately invest in good tools – including the way I use AI.
How I work
Show, don't claim – four principles.
Before adopting a solution, I check whether it really fits the problem. That's how I came to shape 110+ UI building blocks of an in-house library that replaces a third-party framework – leaner and faster.
Lean, targeted solutions over universal heavyweights: fewer dependencies, clearer responsibilities, better performance.
Automated quality gates (lint → typecheck → test → build) and traceable commits – so a team can keep building fast and safely.
Apprentice, intern or team – I share knowledge instead of hoarding it. Including how to use AI sensibly in everyday development.
Tech stack
Tools and technologies I work with every day.
AI – deliberately built
I don't reach for AI at random – I deliberately define how it works: a system of specialised AI agents with clearly documented workflows. At work and in my own projects I steer the AI tooling through dedicated configuration files.
AI with high leverage, not blind trust.
What I own at work
For almost three years I've worked on the frontend of a multi-brand e-commerce system – today across four brands. I look after not just the shop but the system around it – across eight subsystems. I think in connections, not isolated tasks.
Developer Akademie — Intensive web developer training focused on modern frontend development.
What I build
Personal projects – for learning, experimenting and the joy of building.
Sharing knowledge
What I know, I pass on – within the team and beyond.
What others say
Contact
Fancy a chat? Drop me a line directly – I'll get back to you soon.
Or find me here: LinkedIn
Beyond code
Two hobbies, the same way of thinking as programming – expand for the connection.
Every trick follows the same path: countless failed attempts, small corrections, until the movement clicks. Sports neuroscience shows this kind of repeated, focused practice measurably reshapes the cerebellum and keeps the brain in a constant state of neuroplasticity. The same love of iteration – try, learn from the failure, try again – is what I bring to programming.
Someone who reads a board quickly isn't seeing 60 individual cards – they're seeing familiar configurations. That's the same “chunking” cognitive science has documented in experts since Chase and Simon's chess studies (1973), later confirmed in fields like radiology, aviation and business forecasting. That exact pattern-recognition-over-memorising is how I read code: familiar bug and architecture patterns jump out, instead of calculating every line from scratch.