Eventually Inconsistent

The question isn’t whether you are ready for AI. It’s whether your data is. Because some organizations have been recording their history for years — and others are still only keeping snapshots. The difference doesn’t show much today, but it soon will. Where AI meets Event Sourcing Last week I attended the AXONIQ Conference in Amsterdam, where the main theme was  “Where AI meets Event Sourcing.” It wasn’t my first time at that conference — but this time I joined literal round-table discussions . Architects, C-level leaders, and AI specialists sitting together, finally having the kind of conversations that felt overdue. Those discussions were eye-opening — not because of any new revelation about AI itself, but because it became clear what Event Sourcing has quietly been preparing us for all along. Decades of recording intent, state changes, and causality — and only now the world is catching up to why that matters. The gap is already here I’m not an AI expert. But I am a...

 Almost three weeks ago, I participated in an internal AI hackathon. The idea was simple: one day to work on any work-related project, with one constraint — rely almost entirely on AI to do the work. Code generation, design help, scaffolding, naming things, documentation, the works. Naturally, I didn’t pick something easy. I decided to refactor a core part of our system — something foundational, messy, and grown over time. You know me — if there’s domain complexity, some bounded context hairball, or a little #DDDesign chaos to untangle, I’m in. It was the first time I leaned this heavily on AI in one go. Here’s what I learned. If someone tells you AI is writing ALL their code — be skeptical. In some corners of the internet, it sounds like AI can just build entire systems from scratch. In reality? If AI is writing everything for someone, either the task is trivial, or they’re cutting corners you probably don’t want to cut. In my case, the domain was non-trivial, the logic...