Technology should be your greatest driver of growth, not your biggest source of debt. Senior-level engineering expertise — distilled into actionable strategic knowledge.
Featured · Architecture
Almost every engineering team has an architecture diagram that is wrong. Not dramatically wrong — just quietly, incrementally wrong. A dependency added three sprints ago. A service decommissioned six months back still appearing on the board.
Read the essay →Every Lambda invocation writes a tiny REPORT line to CloudWatch. At scale, those 200-byte lines routinely account for 20–60% of a serverless platform’s logging bill. Here is the math, the detection queries, and five concrete fixes — with a real audit example that cut €4,310/month to €890.
Jedes Engineering-Team hat ein Architekturdiagramm. Fast jedes Engineering-Team hat ein Architekturdiagramm, das falsch ist. Nicht dramatisch falsch — nicht fehlende gesamte Subsysteme oder Services, die
Every engineering team has an architecture diagram. Almost every engineering team has an architecture diagram that is wrong. Not dramatically wrong — not missing entire
Wenn du in einem Unternehmen arbeitest, das mehr als eine Handvoll Services betreibt, kennst du das Problem bereits. Jemand tritt dem Team bei und fragt:
If you work at a company running more than a handful of services, you already know the problem. Someone joins the team and asks “which
Claude mit WordPress zu verbinden erforderte früher benutzerdefinierte REST-API-Integrationen, OAuth-Flows und stundenlange Entwicklerarbeit. Im Jahr 2026 ändert das Model Context Protocol (MCP) das vollständig. Du
The Architect’s Edge
One essay per month — distilled from real client engagements, open-source work, and building in public. No fluff. No AI filler. Just thinking that earns your time.
No spam. Unsubscribe at any time.
