Creative developer based in Herne, Germany. I move between design and development because I never found the dividing line between them especially useful. An interface can work perfectly and still feel wrong; a strong visual idea can look great and collapse the moment it has to behave. That tension is what keeps me interested.
I began with HTML, CSS and JavaScript, learning line by line by building things and breaking them. The first goal was simple: make something appear in a browser and understand why it appeared there.
01
code
Design entered the picture
The more I built, the more obvious it became that code was only half the problem. Typography, spacing, colour and composition changed how I looked at interfaces, so graphic design became part of the same learning path rather than a separate discipline.
design
Ten art directions, not one look
Ten finished sites, ten different visual languages, no two of them alike. Self-initiated · 2020–2026.
index.html, styles.css, script.js for most of them — no framework, no build step, no package manager. Nothing to keep updated on a schedule, nothing that breaks because a dependency moved underneath it, and I can open any of them years later and still read what they say.
design
Learning by building
Most of the web projects on this site are self-initiated concept builds. I create the brief, choose the direction, design the interface and work through the implementation myself. Not commissioned work — a record of how I think and what I can build.
03
code
Drawn in the browser instead
Three of the ten have no photographs at all — those interfaces are inline SVG and CSS. They stay sharp at any size, they cost almost nothing to load, and recolouring the whole set is a change to a handful of values.
design
AI as a tool
AI became another layer of the workflow: useful for exploration, research, iteration and testing ideas. I treat it as a tool, not a substitute for judgement.
04
code
Websites, mobile apps, e-commerce
Websites and web apps are where most of the work sits and where every write-up comes from. Mobile app interfaces and e-commerce concepts are the other two areas I explore, alongside graphic design and identity work.
the working method
How I actually work
The method is short enough to state in full. Most sites I build are three files a browser reads on its own: one for the structure, one for the look, one for the behaviour. Nothing is compiled, nothing is bundled, nothing is installed to make it run.
What that buys me is unglamorous and it is the whole point. There is no build to break, so a site that works this year still works in two without being rebuilt to keep pace with its own tooling. There is nothing proprietary inside it, so I don't have to relearn my own choices to fix a typo years later. And the code is small enough to read end to end, which is the only reason I can honestly invite anyone to read it.
Today I keep moving between interfaces, code, identities and experiments — learning by making complete things rather than collecting unfinished exercises.
Accessibility is part of how the thing gets built rather than a pass over it at the end — built to WCAG 2.1 AA practice, which is a way of working and not a certificate.
herne, de · where both halves happen
the certificate
Where the rest of it is
Nobody commissioned the ten builds on this site. The argument for why all my work is self-initiated — what it is worth, and more usefully what it is not — has a page of its own. Or skip it, open the ten builds, and form your own view first.
Google AI Essentials, Coursera. A structured introduction to practical AI workflows, prompting and responsible use — one part of an ongoing learning process. It is not a web, design or accessibility qualification and I am not going to dress it up as one.
google ai essentials · coursera
Today
I keep moving between interfaces, code, identities and experiments — learning by making complete things rather than collecting unfinished exercises.
