Software, mostly
I write about software development. Not often: only when I feel like it and when I think I have something worth sharing.
Recent
Commands and events travel through the same pipes, but they differ in intent, audience and, above all, in who owns the contract. Event Storming helps you find the stories your business tells, and bounded contexts tell you who owns each one.
Why "you don't need a harness" makes sense for someone working on frontier models, but not as general advice, and which parts of a harness are worth keeping.
Sometimes we don't need ultra-sophisticated machinery to run a discovery exercise on legacy software, and AI can be a great help.
Events can reduce coupling, absorb load and help systems scale, but you pay for them in complexity.
We picked practices by weighing cost against benefit, and AI has changed both sides of the scale. A tour of which practices get cheaper, which feed the model's context and tools, and where to be careful.
Vague claims like some users are affected need enough context before they can support a decision.