DISQUS

Sergio Bossa · 3 years ago

Hi Johannes,

I agree with you in many points: yes, we surely tend to look too much toward what will happen in the future.
I just disagree when you say that instead of creating elegant solutions we should keep everything simple; yes, everything should be kept as simple as possible, but this doesn't exclude good, elegant and reusable solutions: there should be some kind of middle ground.

Moreover, I think that up front development and testing of the domain model, in isolation with other layers, helps in focusing to current, real, requirements, because coding the domain model is all about solving your real problems.

My 2 euro cents.

Cheers,

Sergio B.

Johannes Brodwall · 3 years ago

Hi Sergio,
Thank you for you comment

I agree. "Elegant" is not a good word for what I wanted to express. Maybe "perfect" would be better. When it comes to creating reusable solutions, I try and avoid creating reusable solutions "up front", and instead evolve them in a more myopic fashion.

When it comes to domain models, I think our experience is different. I create a skeletal domain model early, then I usually let the rest evolve as I need it. I think both approaches can be valid. Of course, before putting code into production, I like to check what freedom of motion I have left with the database schema.


~Johannes