Essays, notes, and posts
I write about software development. Not often: only when I feel like it and when I think I have something worth sharing.
Recent
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.
The actor model is old, simple and rarely used. Its two primitives, how it handles concurrency, and how I used it in Akka.NET to build a small monitoring tool for on-premise installations.
Building the right software has more to do with telling than with programming. Every story manipulates a little, so own the story and pick the tool that fits your context, from impact mapping to the C4 model.
Complexity feeds on our decisions, and we make the biggest ones when we know the least. Some real examples of keeping it in check, from a stream on top of SQL Server to an outbox in a 20-year-old legacy system.
Practical tips for running Event Storming sessions, from treating the format as flexible to thinking in business facts instead of domain events and practicing before facilitating.