Blog
Articles on the topics where software initiatives are won or lost.
Field notes
Concrete examples, patterns and experience.
Event SourcingField notes
Event sourcing or CRUD with a history table? An honest comparison
A history table is cheaper, faster to add and in many cases enough. Where it holds, where it breaks — and how to tell the difference in advance.
Event SourcingField notes
Retrofit an audit trail or rebuild: when each path pays off
An audit asks for evidence the system never produced. Retrofitting is cheaper — up to a point. This article describes where that point is and how to recognise it.

Event SourcingField notes
Who skipped the credit check? Order fulfilment across five systems
One wrong delivery, five systems, three hours of searching — and a simple new approval rule costs eight weeks. A worked example from B2B distribution: how an event foundation solves traceability and changeability at once.

Event SourcingField notes
Who promised what? When nobody can reconstruct what happened
A customer asks about a commitment made months ago. Five people spend two and a half hours across six tools — and the results contradict each other. A worked example of how a single source of truth makes that question answerable.
Event SourcingField notes
Event modeling is not an architecture tool — it is an adoption tool
Event modeling is sold as a technique. Its biggest effect lies elsewhere: business and engineering see the same picture for the first time and decide together what gets built.
Event SourcingField notes
Event sourcing without fear: when it pays off and when it doesn't
Event sourcing is often seen as a risk. In reality it is a tool with a very specific use case: wherever the history of data matters more than its current state.
Foundation
The underlying stance on this area — why we work the way we do.
Event SourcingFoundation
Software that lasts: why we start with the domain — not with the stack
Most systems do not fail because of the technology choice, but because nobody understood the domain properly. On event modeling, event sourcing and ownership as the foundation of durable software.
Notes
Short thoughts, links and videos.
Event SourcingNote
Bolt-on logging: where is the truth?
AI takes the burden of human vagueness off us. So why do we place a second vagueness — a log — next to our core processes?