Comments on: First principle of design refined http://www.udidahan.com/2007/05/12/first-principle-of-design-refined/ Enterprise Development Expert & SOA Specialist Wed, 10 Mar 2010 11:06:57 -0600 http://wordpress.org/?v=2.8.4 hourly 1 By: » Interfaces solve visibility and testing issues http://www.udidahan.com/2007/05/12/first-principle-of-design-refined/comment-page-1/#comment-2041 » Interfaces solve visibility and testing issues Mon, 04 Jun 2007 09:09:17 +0000 http://udidahan.weblogs.us/2007/05/12/first-principle-of-design-refined/#comment-2041 [...] way to package your code to make sure this occurs follows a very simple design principle. This is much easier to put in practice on new development, but you’ll find that it [...] [...] way to package your code to make sure this occurs follows a very simple design principle. This is much easier to put in practice on new development, but you’ll find that it [...]

]]> By: Evan http://www.udidahan.com/2007/05/12/first-principle-of-design-refined/comment-page-1/#comment-1738 Evan Tue, 15 May 2007 05:05:14 +0000 http://udidahan.weblogs.us/2007/05/12/first-principle-of-design-refined/#comment-1738 I left my thoughts in a post here: http://www.evanhoff.com/archive/2007/05/15/14.aspx They were a bit long, and I didn't want to hijack your blog. ;-) Evan I left my thoughts in a post here:
http://www.evanhoff.com/archive/2007/05/15/14.aspx

They were a bit long, and I didn’t want to hijack your blog. ;-)

Evan

]]> By: Chris http://www.udidahan.com/2007/05/12/first-principle-of-design-refined/comment-page-1/#comment-1733 Chris Mon, 14 May 2007 22:45:33 +0000 http://udidahan.weblogs.us/2007/05/12/first-principle-of-design-refined/#comment-1733 Actually I totally agree with Udi here.. interfaces are useful for things like mocking & TDD, even if only one class implements one interface. Actually I totally agree with Udi here.. interfaces are useful for things like mocking & TDD, even if only one class implements one interface.

]]> By: thesoftwaresimplist http://www.udidahan.com/2007/05/12/first-principle-of-design-refined/comment-page-1/#comment-1712 thesoftwaresimplist Sun, 13 May 2007 06:15:46 +0000 http://udidahan.weblogs.us/2007/05/12/first-principle-of-design-refined/#comment-1712 Well, if over the past three years of my blogging, this is the first time you disagree, I'm quite pleased with myself :) Since I use interfaces to model the roles in a system, according to the Object-Role Modeling "philosophy", I don't get many extraneous interfaces. It's possible that this principle holds strongest when doing ORM. Or, maybe it's the other way around. Maybe this principle can lead developers to ORM. That is what I'm hoping for. Well, if over the past three years of my blogging, this is the first time you disagree, I’m quite pleased with myself :)

Since I use interfaces to model the roles in a system, according to the Object-Role Modeling “philosophy”, I don’t get many extraneous interfaces. It’s possible that this principle holds strongest when doing ORM.

Or, maybe it’s the other way around. Maybe this principle can lead developers to ORM. That is what I’m hoping for.

]]> By: Andrew Sacamano http://www.udidahan.com/2007/05/12/first-principle-of-design-refined/comment-page-1/#comment-1709 Andrew Sacamano Sun, 13 May 2007 01:33:15 +0000 http://udidahan.weblogs.us/2007/05/12/first-principle-of-design-refined/#comment-1709 Udi, for once I disagree with you. Actually, I don't disagree with the idea, I just think you need a few more criteria. I have seen a few too many examples of people mindlessly cluttering their code with interfaces which exactly mirror the design of the only class which implements them, and complicating their build and deployment processes unnecessarily. Perhaps it could be "For any classes A and B in separate modules of a system..." Or maybe I'm thinking of lower level of design from what you are thinking of, and that needs to be called out. But as long as the thought of interfaces is always in one's mind, I think its fine to occasionally let classes just work together. Udi, for once I disagree with you. Actually, I don’t disagree with the idea, I just think you need a few more criteria. I have seen a few too many examples of people mindlessly cluttering their code with interfaces which exactly mirror the design of the only class which implements them, and complicating their build and deployment processes unnecessarily.

Perhaps it could be “For any classes A and B in separate modules of a system…” Or maybe I’m thinking of lower level of design from what you are thinking of, and that needs to be called out. But as long as the thought of interfaces is always in one’s mind, I think its fine to occasionally let classes just work together.

]]>