built to last
I solve problems.Mostly on the web.
Full-stack developer today, sound engineer for ten years before that. In between, always the same question: why does a system work, and where does it slow itself down? The blog collects whatever sticks along the way.
About me
A developer with an engineer's mind
Today I build web applications as a full-stack developer: TypeScript, React, Vue and Next.js in the frontend, APIs, TYPO3 and headless CMS behind it. Before that I spent ten years doing sound for theatres, studios and events. I studied electronics and telecommunications, specialising in audio engineering.
What stayed is the urge to understand things before touching them. Whether it is a signal chain, a database or an editorial workflow.
How I approach things
Approach
How I approach things
- 01
Understand first
Before anything gets built, one question comes first: how does the system work, and where does it slow itself down? Whether it is legacy code, an API or an editorial workflow.
- 02
Measure like an engineer
Load times, contrast, error rates. If it can be measured, I don't debate it for long, I measure it.
- 03
For the people using it
A system is only done when others can run it without me. Editors, tech teams, visitors.
Questions on my mind right now. In code, in the team and somewhere in between.
- How much code do I still write myself?
- Why is the build only red in CI?
- When is a system done?
- What makes a CMS usable?
- No deployments on Friday?
- Accessible from line one?
- What measures good performance?
- What is left when AI codes?
Good solutions happen where technology and people overlap.
Contact
Let's talk
A question about a post, a tricky problem or just up for a chat? Write to me. About technology, work, or why deployments on a Friday afternoon are never a good idea.
