A look into the disruption driven by AI on software, with a long detour on Serverless, and a spicy touch of disagreement with Simon Wardley
The sense of the Past
In the first post of this series we wondered how an application based only on Events would look like. To construct a proof of concept for this idea, in this second post we investigate data persistence under a different view.
Imagine a software application based only on Events. How would it be? And, what benefits that kind of architecture would bring?
Fiction in software – part two
If narratives are just fiction, why do they matter? In this second part of the series, we explore our true nature as storytellers, and what happens when software application projects fail.
Fiction in software – part one
Fiction narratives lay in the core of software design. This first part in a series of two explores two examples: a narrative based on transactions, and a narrative based on Events.
Into the timestream
Let's continue our exploration of the Domain and its representations in the code, we make a look into the timestream!
The role of Domain Coach
How can we make the most of the Domain-based methodologies to create software? The Domain Coach may a good answer to this question. But, wait, what is a Domain Coach?
But, what is the Domain?
If the Domain was a Universe, the vast collection of models that we create in our code to represent it would be a Multiverse.
Dumb by the pattern
Are we developers software crafters, or mere pattern implementors?
Architecture tests check that software keeps in full compliance of architecture decisions (or ADRs) after code changes were committed.