When I analyse the code of a legacy application, or of an application built with hexagonal architecture, I have a hard time finding the logic that belongs to a business feature such as cancelling a policy. I have to open 14 files and I'm completely lost. A non-technical person has no chance of understanding the code.
I recently talked with one of our lead engineers, and the conversation stayed with me. He finds the new reality hard to accept, and he isn't the only one. AI and agentic coding are changing how we work.
From explicit page composition to a registry of slice-owned components. We have worked through the business process together. The Event Model shows what the user sees, which commands they can issue, which events record the outcome, and which views provide the information for the next step.
You can't ship without a human in the loop if you don't know what you're shipping. Continuous deployment is often sold as a pipeline problem. Write the tests, automate the stages, remove the approval button. But in a regulated environment, the approval button rarely exists because someone distrusts the tests. It exists because nobody can say, with evidence, what is inside the thing being deployed.
Dynamic Consistency Boundaries give us another way to think about correctness in event-sourced systems. Consistency belongs to decisions, not to aggregates.
A software development process can look remarkably healthy while producing very little. The planning happens. Tickets move. Documents are written and reviewed. Meetings fill the calendar. Each role completes its…
AI can produce more software, more documentation, more tests, more pull requests and more analysis than humans can reasonably consume. At first sight that looks like an obvious productivity breakthrough,…
In some of my recent articles I have argued that AI will not fix a broken SDLC, and that we need a blueprint before we hand work to an agent.…
“Business doesn’t know what it wants.” I have heard engineers say this in many companies, usually with plenty of examples to support the claim. Requirements change, important details surface late,…
There is one observation that has followed me throughout my career, regardless of the company, the industry or the technology involved. Whenever a software initiative began to struggle, the first…