Comments on: No silver domain modeling bullets http://lostechies.com/jimmybogard/2010/03/11/no-silver-domain-modeling-bullets/ Strong opinions, weakly held Wed, 19 Jun 2013 17:39:00 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: Henrik http://lostechies.com/jimmybogard/2010/03/11/no-silver-domain-modeling-bullets/#comment-3624 Henrik Sun, 24 Jul 2011 11:15:00 +0000 /blogs/jimmy_bogard/archive/2010/03/11/no-silver-domain-modeling-bullets.aspx#comment-3624 I would argue that there's a role for modelling if the model is also used for programmatic decision making. Now, I have no experience the the object role modelling that you are talking about, but I understand the concept of creating an ontology - and an ontology can be used for algorithmic reasoning, such as argumentation or planning logic. On the other hand, you are correct in that the source of truth is the code. A lot of computation is about data structures encapsulating data, such as splay trees, other computation about encoding human knowledge, like DDD, other computation about acting on both the human knowledge encoded and the data structures. I think this will lead to languages that are more homoiconic in the long run, i.e. where the code IS the data IS the ontology. I would argue that there’s a role for modelling if the model is also used for programmatic decision making. Now, I have no experience the the object role modelling that you are talking about, but I understand the concept of creating an ontology – and an ontology can be used for algorithmic reasoning, such as argumentation or planning logic.

On the other hand, you are correct in that the source of truth is the code.

A lot of computation is about data structures encapsulating data, such
as splay trees, other computation about encoding human knowledge, like
DDD, other computation about acting on both the human knowledge encoded
and the data structures.

I think this will lead to languages that are more homoiconic in the long run, i.e. where the code IS the data IS the ontology.

]]> By: Josh Arnold http://lostechies.com/jimmybogard/2010/03/11/no-silver-domain-modeling-bullets/#comment-2235 Josh Arnold Thu, 18 Mar 2010 18:43:46 +0000 /blogs/jimmy_bogard/archive/2010/03/11/no-silver-domain-modeling-bullets.aspx#comment-2235 I think you're spot on here, Jimmy. I was once on the bandwagon of pushing for the code-generation aspect of ORM (both SQL and the domain model in code) but it didn't take long for me to run into too many problems. As you said, it's a great starting point. During my little journey through the world of ORM, I felt like it became pretty clear that it's great at facilitating one thing: communication. Perhaps the best way to describe it is that it helps remove ambiguity and makes it easier to talk about your domain. Rather than spending time clarifying relationships, you have a structured way of discussing the meaning of the relationships. The title of this post is perfect. My fear would be that anyone that starts using ORM would view it as a silver-bullet. It's simply another tool to help with the process of modeling a domain. I think you’re spot on here, Jimmy. I was once on the bandwagon of pushing for the code-generation aspect of ORM (both SQL and the domain model in code) but it didn’t take long for me to run into too many problems. As you said, it’s a great starting point. During my little journey through the world of ORM, I felt like it became pretty clear that it’s great at facilitating one thing: communication. Perhaps the best way to describe it is that it helps remove ambiguity and makes it easier to talk about your domain. Rather than spending time clarifying relationships, you have a structured way of discussing the meaning of the relationships.

The title of this post is perfect. My fear would be that anyone that starts using ORM would view it as a silver-bullet. It’s simply another tool to help with the process of modeling a domain.

]]>