- I have worked on the web since 2011, starting with an apprenticeship. - Since then I have worked in agencies and product companies, and led - the frontend team at an agency. I have been fully remote since 2021 - and am now independent, while running a small product business. -
-- Design and frontend are my strength. I am comfortable with backend - concepts and architecture. Today I mostly write TypeScript and - Next.js, plus Rust and Solidity for systems work. The path started - with Vue and plain JavaScript, and I would rather say so than pretend - I always wrote Rust. -
-
+ {OWNER.name}
+
+ {OWNER.street}
+
+ {OWNER.city}
+
+ {OWNER.country}
+
+ Email:
+ VAT identification number according to section 27a of the German VAT + Act (Umsatzsteuergesetz): {OWNER.vatId} +
+{OWNER.name}, address as above (section 18 paragraph 2 MStV).
++ I am neither willing nor obliged to take part in dispute resolution + proceedings before a consumer arbitration board. +
+- - {" · "} - {readingMinutes} min read -
- - {tags.map((tag) => ( -- - {" · "} - {note.readingMinutes} min read -
-- {note.summary} -
- - {note.tags.map((tag) => ( -+ I have been building for the web for 15 years: first in agencies, + later as a senior developer, and now on my own. +
++ My strength is the part people see and use: design and interface. I am + also at home with what lies behind it, so I can build a complete + application and not just its surface. +
++ You work with me directly. Whether you run a product team or are + commissioning something like this for the first time. +
+The path so far
++ In most companies, people move information from one tool to another: + read it here, type it in there, send an email about it. Automation + connects those tools so that the work passes from one to the next on + its own. Three typical examples: +
+{group.title}
+{group.title}
+What I work with
++ {group.area} +
++ Software is connected: a change in one place can break another. I + secure what I build with automated tests, and every change has to + pass them before it is released. This is what such a run looks + like. +
+{item.text}
++ Besides client work I build my own software, among other things a + system in Rust and Solidity that runs on seven blockchains. +
+
+ {OWNER.name}, {OWNER.street}, {OWNER.city}, {OWNER.country}.
+
+ Email:
+ This website sets no cookies, shows no advertising and includes no + content from third parties. Fonts and images are served from this + website itself. +
++ When you open a page, the server processes technical data that your + browser sends: your IP address, the time, the page requested and the + browser type. This is necessary to deliver the website and to keep it + secure. The legal basis is my legitimate interest in running the + website (Article 6(1)(f) GDPR). +
++ I count page views with Umami, which I run on my own server. It works + without cookies and does not create profiles of individual visitors. + The data is not passed on to third parties. The legal basis is my + legitimate interest in understanding how the website is used (Article + 6(1)(f) GDPR). +
++ If something on this website fails technically, an error report is + sent to an error tracking service that I run on my own server. It + contains technical details such as the page, the browser and the error + message. Sessions are not recorded. The legal basis is my legitimate + interest in a working website (Article 6(1)(f) GDPR). +
++ If loading a page fails, the website stores a timestamp in your + browser's session storage so that it reloads only once. It is + deleted when you close the tab and is not sent anywhere. +
++ If you send me an email, I process what you write and your address in + order to answer you and, if it comes to that, to prepare a contract + (Article 6(1)(b) GDPR). I keep the correspondence for as long as it is + needed for that purpose or as the law requires. +
+You have the right to:
+
+ To use any of these rights, write to
- One running example: parsing an availability, meaning a date and - weekly hours. The date 2026-02-30 must be rejected, 2028-02-29 must be - accepted, and 168 hours is the upper boundary of a week. -
-- {line} -
- ))} -- - Download the sample report (sample-delivery-report.md) - -
-- AI-built code often arrives with few tests, or with tests that only - repeat the implementation. I do not start by rewriting. I write the - expected behavior as cases for the parts that matter most, run them - against the existing code, and let the failures show what is really - broken. Then I add a mutation baseline so you can see which tests - would not notice a bug. -
-- Coverage tells you which lines ran during the tests. It does not tell - you whether the tests would notice a bug in those lines. Mutation - testing changes the code on purpose and checks that a test fails. That - is the question you care about. Coverage stays useful as a gap finder: - it points at code nothing exercises. It is not a goal, and a high - number alone proves little. -
-- Two systems where I run this: a Rust and Solidity liquidation system - across 7 chains, with a zero-survivor mutation gate and a coverage - ratchet, and the domain core of this website, which has its own tests - and mutation gate. -
-- {item.text} -
-- A 20-minute intro call is enough to see whether this fits your team. -
-- {posts.length} post{posts.length === 1 ? "" : "s"} -
-- {tech.subtitle} -
-- {tech.description} -
-- {tech.customerValue} -
-{{ERROR}}
