Hello! Thinking inside a bigger box is using DISQUS, a powerful comment system, to manage its comments. Learn more.
Community Page
- www.brodwall.com/johannes/blog/ Jump to website »
-
Subscribe -
Community
-
Top Commenters
-
Popular Threads
-
Recent Comments
- The evolution of SOA Introduce the concepts of services and SOA Design principles of SOA ... The benefits of employing SOA Review of common business goals ... Related articles. Web Application...
- Great article and I agree with you that ............ Thanks for the tips!
- Great read, good work old chap :)
- Hi...Your post really got me thinking man..... an intelligent piece ,I must say.
- Was a good read. thank great post, I think this article is useful. I'll be back for more. Thanks for sharing the information . .. :)
Jump to original thread »
Myopia: the inability to see distant objects as clearly as near objects. PreferredConsumer.com
What makes a good statement? In my experience, a good statement is one that people will disagree with frequently. One of the internal quality auditors at my company has an excellent plaque in her o ... Continue reading »
What makes a good statement? In my experience, a good statement is one that people will disagree with frequently. One of the internal quality auditors at my company has an excellent plaque in her o ... Continue reading »
2 years ago
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.
2 years ago
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