Domain Driven Development emphasizes that the software is a model, but what does it really mean for software "to be a model"? How does that definition impact in what we understand by "good design"? What are the differences of our models with the ones of other professions and how they impact in the design and development we do?
Current trends in software development and the design of many class libraries and frameworks show that we still don't fully understand what modeling means and how that impacts our profession at a technical, administrative and human level.
In this talk we will try to synthesize the basics of software design from understanding what modeling with software is. We will see how it affects our designs the way we interpret the problem domain, how to map it to our model, how to represent the pass of time on it and the importance for our models to teach us how to use them.
From that synthesis we will derive, using practical examples, a set of very simple but powerful design heuristics that will change the way you design software forever.