Most AWS writing picks one lane: deep-technical, or strategy thought-leadership. The seam I live in is three layers at once — the architecture, the commercial mechanics underneath it, and the AI-augmented way the work actually gets delivered. Very few people write credibly across all three, because doing all three is rare. That intersection is this blog's reason to exist.
What you'll find here
Every claim is grounded in numbers I've actually worked, not estimates waved at a slide. Migration economics down to the funding formulas. Modernization war stories with real latency figures and real cost build-ups. The scoping seam where technical reality meets a fixed-price SoW. AI inside genuine SA workflows, as field notes rather than speculation. When a cost model appears, the arithmetic is shown — that transparency is the credibility.
What you won't
- re:Invent recaps.
- "10 best practices" listicles.
- Vendor-neutral fence-sitting.
Everyone writes those and none of them sound like anyone. The promise here is simpler: you'll leave knowing something you can use, backed by numbers, said plainly by someone who's done it.
The bias
Opinionated, and willing to say don't. Concise by default — short pieces that land beat comprehensive ones nobody finishes. Trenches, not vendor. If a post hedges every claim, I've failed at it.
Contact
- techno@encc.de
- /in/your-handle
- Based in
- Germany