To become a software crafter…Or die in the attempt.

Posts by ouarzy:

Time-Aware design

Time-Aware design

I already advocated how an Event Driven Architecture allows our code to be more aligned with our business. Mike has the same conclusion, focusing on Practical Event Sourcing. But why such a system is by design more aligned with the business?Because it tells a story  Good code must tell a […]

Coding in N dimensions

Coding in N dimensions

I discovered this year Carlo Pescio‘s work on the physics of software. He has a scientific approach of software design. This video from DDD Europe is a good way to discover his work. Combined with the amazing talk from James Coplien, it gives me a lot of things to process since […]

Make the implicit explicit

Make the implicit explicit

It is really hard to manage, or explain what we can’t see. Based on this statement, we should continuously look for ways to reveal the important implicit concepts in software. It is our chance to explain what software is to people who don’t look at lines of code all day long. […]

The Technical Debt Myth

The Technical Debt Myth

We assume that less design effort allows producing features faster, in the short term.  Less design effort generally means less abstraction, and tighter coupling, in order to produce working code faster. But we tend to overlook the fact that it slows future modifications, even of unrelated features, because of tight […]

Daily DDD

Daily DDD

From the mouths of lots of DDD practitioners, and from Eric himself, we often hear DDD is hard. In my opinion it would be more correct to say DDD is huge. Trying to understand it from scratch, as a whole, is like trying to understand a huge code base as a […]

Clarifying MVVM with DDD

Clarifying MVVM with DDD

I regularly see a lot of questions around MVVM, last one only a few weeks ago. The problem is usually the same: what should be a Model, and what should be a ViewModel? We can’t really blame developers, because references online are not really good, especially MSDN’s one. The explanation […]