Software architecture & applied AI
Calm notes on building software and AI systems that last.
Personal notes on software architecture and applied AI — with a focus on reliability, responsibility, and long-term operability.
Written from Linz, Austria — collaborating globally
Practice
Systems thinking for teams shipping software and AI in the real world.
Architecture reviews, delivery guidance, and writing shaped around reliability, operability, and long-term leverage.
Architecture
Make the technical shape legible.
Clarify boundaries, failure modes, and the operating model before complexity hardens into process.
AI Delivery
Ship applied AI without the theatre.
Bring evaluation, governance, and backend discipline into systems that need to behave under real load.
Advisory
Give leadership a calmer decision surface.
Support founders and CTOs with direct sparring on tradeoffs, sequencing, and durable technical bets.
Projects
Things I build and help run.
A product company and an open-source library — both built on the same bias for reliable, operable systems.
Localization platform
LingoHub
A translation-management platform that helps software teams ship products in every language — continuous localization wired directly into the developer workflow.
Open source · Java
Threadmill
A modern replacement for Quartz and JobRunr — durable, clustered background jobs and scheduling for Java 25 behind one small, idempotency-first API.
Writing
Recent field notes.
Design Your Solo SaaS for Operational Continuity, Not Faster Code
AI speeds development, but solo SaaS fails on coverage. Design for migrations, incidents, succession, and a bus factor greater than one.
Read →Aug 10, 2026Do Not Run Bedrock Guardrail Checks on Every Agent Turn
AWS's resourceless InvokeGuardrailChecks API moves guardrail policy into code. Why blanket per-turn checks break your quota and miss real trust boundaries.
Read →Aug 09, 2026The METR Study Flipping Sign Is Not Permission to Raise Your Velocity Targets
A sign-flipping AI productivity study cannot justify higher velocity targets; CTOs should measure review pressure, failures, and recovery instead.
Read →Working through a hard architecture or AI decision?
Direct sparring for founders and CTOs on tradeoffs, sequencing, and durable technical bets.