Blog

Gedanken zu KI-gestützter Entwicklung, Engineering-Leadership und dem Bau skalierbarer Software.

KI & Automatisierung

Managing 6 Engineering Clients with AI Workflows

How AI-augmented development workflows enabled managing 6 concurrent engineering clients across different agencies without sacrificing quality.

January 28, 2026

Engineering

engineering2 Min. Lesezeit

Open to work. Here's exactly what my first week on your team looks like, no ramp-up theater.

Open to work, what my week 1 looks like

August 14, 2026

engineering2 Min. Lesezeit

Every morning I open an app I built and read the jobs it thinks I should apply to. This post came from one of them.

I dogfood, ApplyPulse finds my own jobs

August 13, 2026

engineering2 Min. Lesezeit

Apple rejected my app. The reason still makes me wince, because it was completely fair.

Apple rejected my app, and the reason was fair

August 12, 2026

engineering1 Min. Lesezeit

A camera at a gate reads your license plate and decides if it opens. I built that without sending a single image to the cloud.

Self-hosted computer vision (ALPR) at the edge

August 11, 2026

engineering1 Min. Lesezeit

I volunteered to build the thing every engineer avoids: integrating with a Latin American tax authority.

LATAM e-invoicing nobody wants to build

August 10, 2026

engineering1 Min. Lesezeit

When you hire me, you get more than a feature factory. You get the person who makes the next ten features cheap.

Open to work, hire the platform thinking not just the dev

August 7, 2026

engineering1 Min. Lesezeit

Every SaaS I build is multi-tenant on day one. Retrofitting tenancy later is how startups get a data-leak headline.

Multi-tenant from day one

August 6, 2026

engineering1 Min. Lesezeit

My rule for shared code: if the per-app adapter is longer than 50 lines, the abstraction is wrong.

The 50-line adapter rule

August 5, 2026

engineering1 Min. Lesezeit

Unpopular opinion: most "AI bugs" are actually input-trust bugs wearing a costume.

Every external input is adversarial

August 4, 2026

engineering1 Min. Lesezeit

One Express backend serves 13+ different apps. The reason it doesn't break them all at once is 17 contract tests.

One backend, 13+ apps, contract tests

August 3, 2026

engineering1 Min. Lesezeit

I'm open to work, and I'll save us both time: here are the exact three roles I'm built for.

Open to work, the 3 roles I'm built for

July 31, 2026

engineering2 Min. Lesezeit

Most teams build the web app, then rebuild the whole thing for mobile. I refuse to write it twice.

One core, web and React Native, no rewrite

July 30, 2026

engineering1 Min. Lesezeit

The scariest bug in payments isn't a crash. It's paying someone twice and never knowing.

A payment state machine that can't double-spend

July 29, 2026

engineering1 Min. Lesezeit

83 shared libraries. Dozens of apps depending on them. Here's why a change to one doesn't take down the others.

83 shared libraries without breaking apps

July 28, 2026

engineering1 Min. Lesezeit

A vendor wanted a per-scan fee to read license plates. I replaced them in a weekend and the app never noticed.

Swapped a commercial vendor for OSS behind an interface

July 27, 2026

engineering1 Min. Lesezeit

I'm open to work. Instead of listing skills, here's what I actually shipped in the last month.

Open to work, proof of weekly output

July 24, 2026

engineering1 Min. Lesezeit

0.1 + 0.2 doesn't equal 0.3. If your billing code uses floats, you're already losing money.

Money as integers, fiscal-core e-invoicing

July 23, 2026

engineering1 Min. Lesezeit

A job description tried to hijack my AI. I planned for that before it happened.

Treating scraped job posts as adversarial input

July 22, 2026

engineering1 Min. Lesezeit

I run 20+ apps out of a single monorepo. The trick isn't speed. It's refusing to write the same thing twice.

20+ apps, one monorepo, one reuse discipline

July 21, 2026

engineering1 Min. Lesezeit

The tool that surfaced your job posting to me? I wrote it.

I built the AI that matched me to your job

July 20, 2026

engineering3 Min. Lesezeit

Automated Code Review: Git Hooks + Claude API in Production

Implementing an AI-powered code review pipeline using git hooks and the Claude API that catches 73% of issues before human review.

February 5, 2026

engineering3 Min. Lesezeit

Building AI Agent Architecture From Scratch

How I went from a 2,300-line orchestrator to a composable multi-agent system using TypeScript, YAML configs, and factory patterns.

January 15, 2026

Wird geladen

Blog

KI & Automatisierung

Managing 6 Engineering Clients with AI Workflows

Engineering

Open to work. Here's exactly what my first week on your team looks like, no ramp-up theater.

Every morning I open an app I built and read the jobs it thinks I should apply to. This post came from one of them.

Apple rejected my app. The reason still makes me wince, because it was completely fair.

A camera at a gate reads your license plate and decides if it opens. I built that without sending a single image to the cloud.

I volunteered to build the thing every engineer avoids: integrating with a Latin American tax authority.

When you hire me, you get more than a feature factory. You get the person who makes the next ten features cheap.

Every SaaS I build is multi-tenant on day one. Retrofitting tenancy later is how startups get a data-leak headline.

My rule for shared code: if the per-app adapter is longer than 50 lines, the abstraction is wrong.

Unpopular opinion: most "AI bugs" are actually input-trust bugs wearing a costume.

One Express backend serves 13+ different apps. The reason it doesn't break them all at once is 17 contract tests.

I'm open to work, and I'll save us both time: here are the exact three roles I'm built for.

Most teams build the web app, then rebuild the whole thing for mobile. I refuse to write it twice.

The scariest bug in payments isn't a crash. It's paying someone twice and never knowing.

83 shared libraries. Dozens of apps depending on them. Here's why a change to one doesn't take down the others.

A vendor wanted a per-scan fee to read license plates. I replaced them in a weekend and the app never noticed.

I'm open to work. Instead of listing skills, here's what I actually shipped in the last month.

0.1 + 0.2 doesn't equal 0.3. If your billing code uses floats, you're already losing money.

A job description tried to hijack my AI. I planned for that before it happened.

I run 20+ apps out of a single monorepo. The trick isn't speed. It's refusing to write the same thing twice.

The tool that surfaced your job posting to me? I wrote it.

Automated Code Review: Git Hooks + Claude API in Production

Building AI Agent Architecture From Scratch

Seite wird vorbereitet…

Blog

KI & Automatisierung

Managing 6 Engineering Clients with AI Workflows

Engineering

Open to work. Here's exactly what my first week on your team looks like, no ramp-up theater.

Every morning I open an app I built and read the jobs it thinks I should apply to. This post came from one of them.

Apple rejected my app. The reason still makes me wince, because it was completely fair.

A camera at a gate reads your license plate and decides if it opens. I built that without sending a single image to the cloud.

I volunteered to build the thing every engineer avoids: integrating with a Latin American tax authority.

When you hire me, you get more than a feature factory. You get the person who makes the next ten features cheap.

Every SaaS I build is multi-tenant on day one. Retrofitting tenancy later is how startups get a data-leak headline.

My rule for shared code: if the per-app adapter is longer than 50 lines, the abstraction is wrong.

Unpopular opinion: most "AI bugs" are actually input-trust bugs wearing a costume.

One Express backend serves 13+ different apps. The reason it doesn't break them all at once is 17 contract tests.

I'm open to work, and I'll save us both time: here are the exact three roles I'm built for.

Most teams build the web app, then rebuild the whole thing for mobile. I refuse to write it twice.

The scariest bug in payments isn't a crash. It's paying someone twice and never knowing.

83 shared libraries. Dozens of apps depending on them. Here's why a change to one doesn't take down the others.

A vendor wanted a per-scan fee to read license plates. I replaced them in a weekend and the app never noticed.

I'm open to work. Instead of listing skills, here's what I actually shipped in the last month.

0.1 + 0.2 doesn't equal 0.3. If your billing code uses floats, you're already losing money.

A job description tried to hijack my AI. I planned for that before it happened.

I run 20+ apps out of a single monorepo. The trick isn't speed. It's refusing to write the same thing twice.

The tool that surfaced your job posting to me? I wrote it.

Automated Code Review: Git Hooks + Claude API in Production

Building AI Agent Architecture From Scratch