Domain-Driven Design encourages to analyse the domain deeply in a process called Supple Design. In his book (the blue book) and in his talks Eric Evans gives some examples of this process, and in this blog in several parts I will suggest some sources of inspirations and some recommendations drawn from my practice in order to help about this process.
Principles for using annotations
déc 14th, 2009
Deciding where and how to place the annotations is not innocent. The last thing we want is to create extra maintenance effort because of the annotations. In other words, we want annotations that are stable, or that change for the same reasons and at the same time than the elements they annotate. This article suggests [...]
Many concepts look obvious because they are used often, not because they are really simple. Small quantities that we encounter all the time in most projects, such as date, time, price, quantity of items, a min and a max… hardly are a subject of interest from developers « as it is obvious that we can represent [...]
Pattern grammar for the variant problem
nov 1st, 2009
For tools to be aware of patterns, the patterns must be formalized, at least partially. At this point I must quote Gregor Hohpe to clarify my thoughts, as I strongly agree with his skipticism: Typically, when people ask me about « codifying » or « toolifying » patterns my first reaction is one of skepticism. Patterns are meant to [...]
Patterns express intents
sept 6th, 2009
Patterns represent a couple (intent, solution); sometime they refer to a solution, more often they essentially represents an intent, independently of its solution. Sometimes the solution part of patterns includes a trick or a workaround to overcome the limits of a language, but patterns cannot be reduced to that trick. Indeed, a very important role [...]
Patterns as another kind of types
sept 3rd, 2009
Patterns represent a couple (intent, solution), where the intent matters most. Based on that intents, that can be generic or specialized, I propose to consider patterns like types in languages with strong typing, for the compiler to enforce their constraints. Declaring patterns: what for? Consider the very simple Quantity pattern from Analysis Patterns (Fowler): Represent [...]
Categories
- En français (4)
- General (2)
- Leisure (8)
- Music (16)
- Patternity (12)
- Physical Computing (8)
- Beam Beats (5)
- Programming (56)
- ddd (8)
- Functional style (2)
- Patterns (19)
- Soft skills (1)
-
See my speaking history on lanyrd
I talk about
abstraction accessibility analysis api architecture arduino beam beats beat classdiagram convention ddd dependencies design domain drum machine education electronic experience functional hacking instrument intent interactive interface java language library methodology midi Music musical instrument oo pattern patternity problem Programming research rhythm solution syntax tool trick uml valueobject visualization-
Friends
Web presence
License
All original material of whatever nature created by Cyrille Martraire and included in this weblog and any related page, including the weblog's archive, is licensed under a Creative Commons License.
