Comments on: Design Patterns – Building blocks for your application http://techtracer.com/2007/06/10/design-patterns-building-blocks-for-your-application/ Tracing the course of Web Technology Sun, 13 May 2012 05:47:02 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: melodixofenacn http://techtracer.com/2007/06/10/design-patterns-building-blocks-for-your-application/comment-page-1/#comment-496 melodixofenacn Mon, 30 Jul 2007 07:59:15 +0000 http://techtracer.com/2007/06/10/design-patterns-building-blocks-for-your-application/#comment-496 <strong>melodixofenacn...</strong> nice post... melodixofenacn…

nice post…

]]> By: nitinpai http://techtracer.com/2007/06/10/design-patterns-building-blocks-for-your-application/comment-page-1/#comment-286 nitinpai Mon, 11 Jun 2007 17:38:26 +0000 http://techtracer.com/2007/06/10/design-patterns-building-blocks-for-your-application/#comment-286 Hi Mike, Thanks for your inputs. I have actually mentioned the points that you have stated, please read these lines: <i>In such cases it becomes necessary that the people who will take the application in their hands in future should be in a position to realize the design architecture quickly and start their work on it.<i> <i>Since standard patterns are known to most of the people associated with the same environment it is a high probability that the design will be easier to test, learn and then maintain</i> And it is conversation and communication only when the the other party knows about the patterns you are talking about otherwise it is not much of use, but still a pattern helps to put more clarity into your your architecture and avoids confusion. Hi Mike,

Thanks for your inputs. I have actually mentioned the points that you have stated, please read these lines:

In such cases it becomes necessary that the people who will take the application in their hands in future should be in a position to realize the design architecture quickly and start their work on it.

Since standard patterns are known to most of the people associated with the same environment it is a high probability that the design will be easier to test, learn and then maintain

And it is conversation and communication only when the the other party knows about the patterns you are talking about otherwise it is not much of use, but still a pattern helps to put more clarity into your your architecture and avoids confusion.

]]> By: Mike http://techtracer.com/2007/06/10/design-patterns-building-blocks-for-your-application/comment-page-1/#comment-285 Mike Mon, 11 Jun 2007 16:44:23 +0000 http://techtracer.com/2007/06/10/design-patterns-building-blocks-for-your-application/#comment-285 You forgot another reason. Communication. In two ways. One, when you are looking through the code, and you see a class referenced called PersonFactory, you know, without looking at the implementation of that class, that it implements the Factory pattern, and, assuming you are familiar with that pattern, you know a lot about that class. Also, in conversation, to be able to describe you software to a colleague using pattern names in your discussion allows you to explain a lot about your architecture with fewer words. You forgot another reason. Communication. In two ways. One, when you are looking through the code, and you see a class referenced called PersonFactory, you know, without looking at the implementation of that class, that it implements the Factory pattern, and, assuming you are familiar with that pattern, you know a lot about that class.

Also, in conversation, to be able to describe you software to a colleague using pattern names in your discussion allows you to explain a lot about your architecture with fewer words.

]]>