About

I'm the managing director of a small metal manufacturing company in Germany. Most days I'm on the shopfloor — production lists, supplier calls, the usual rhythm of making things that have to hold.

Evenings and stolen hours, I'm learning to code. Not to become a developer. To stop waiting for permission to fix my own problems.

WERKSCODE is where those two worlds meet.

Why this site exists

For years my digital life was split. At work: systems I couldn't easily change — expensive, slow, built for a different era. At home: ideas for small tools, better documentation, a place to write about learning without pretending I'd been doing it for twenty years.

Every time I started, I made the same quiet deal: keep it private until it's good.

I broke that deal. The GitHub repository is public from day one. The homepage can still say "coming soon" while the git history already shows the messy, honest path. That choice had reasons.

This site is a blog and portfolio — a place to think in public. The manufacturing tools I build for internal use stay private, as they should.

Who you're reading

One person. Not a team, not an agency, not a "we" pretending to be bigger than I am.

I write about learning to code while running a business — especially for self-employed people who wonder whether this is for them. The tone is shopfloor meets software: practical, honest, sometimes funny, never corporate.

If a post sounds polished, it's because I edited it until it sounded like me — not because I outsourced the thinking.

How this site is made

Nuxt 4, Vue, TypeScript, Tailwind, Nuxt Content, PostgreSQL for the contact form. Docker for dev. The stack is documented in the repository README.

AI tools — mainly Cursor — help with drafting, code, and translation. I decide what ships, verify what matters, and keep the stories personal.

For the full picture of how AI is involved, see How I use AI on this site.

Get in touch

Questions, corrections, or just saying hello — contact me. I read everything that comes through the form.