What about design patterns?
-
-
Do you use design patterns? I used
CompositeandSingleton, occasionally.If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
When developing systems nowadays, it is very difficult to develop a system that doesn't have some forms of pattern applied to it. Developing applications is about good design and in the design process, you will discover what patterns apply.
the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer
Deja View - the feeling that you've seen this post before. -
Do you use design patterns? I used
CompositeandSingleton, occasionally.If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
CPallini wrote:
Do you use design patterns?
Yes, and I used
Singletonto restrict the number of connections to the database. After getting benefit from this, now I'm looking for other patterns too, so, recently started studying design patterns -- though its not regular. But during study, noted that self studying design patterns is a bit challenging to understand. How you covered (are covering) design patterns? Regards.________________________________ Success is not something to wait for, its something to work for.
-
CPallini wrote:
Do you use design patterns?
Yes, and I used
Singletonto restrict the number of connections to the database. After getting benefit from this, now I'm looking for other patterns too, so, recently started studying design patterns -- though its not regular. But during study, noted that self studying design patterns is a bit challenging to understand. How you covered (are covering) design patterns? Regards.________________________________ Success is not something to wait for, its something to work for.
uroojkhan wrote:
How you covered (are covering) design patterns?
Like you I'm self studying design patterns (I've the book of Gamma, Helm, Johnson, Vlissides) and, like you, I find them quite challenging. I think that if you need one pattern in you project, then you'll have a chance to deeply understand it. :)
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
-
uroojkhan wrote:
How you covered (are covering) design patterns?
Like you I'm self studying design patterns (I've the book of Gamma, Helm, Johnson, Vlissides) and, like you, I find them quite challenging. I think that if you need one pattern in you project, then you'll have a chance to deeply understand it. :)
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
CPallini wrote:
I've the book of Gamma, Helm, Johnson, Vlissides
Thanks for the book (Design Patterns: Elements of Reusable Object-Oriented Software) reference.
CPallini wrote:
I think that if you need one pattern in you project, then you'll have a chance to deeply understand it.
True. But before using patterns we must have know how about it.:) Thanks and Regards:rose:
________________________________ Success is not something to wait for, its something to work for.
-
CPallini wrote:
I've the book of Gamma, Helm, Johnson, Vlissides
Thanks for the book (Design Patterns: Elements of Reusable Object-Oriented Software) reference.
CPallini wrote:
I think that if you need one pattern in you project, then you'll have a chance to deeply understand it.
True. But before using patterns we must have know how about it.:) Thanks and Regards:rose:
________________________________ Success is not something to wait for, its something to work for.
uroojkhan wrote:
But before using patterns we must have know how about it.
True, of course. But the book we wrote about is of big help, because it first identifies and clarifies the problem the pattern addresses, then explains the details of the pattern itself. Cheers :)
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
-
CPallini wrote:
I've the book of Gamma, Helm, Johnson, Vlissides
Thanks for the book (Design Patterns: Elements of Reusable Object-Oriented Software) reference.
CPallini wrote:
I think that if you need one pattern in you project, then you'll have a chance to deeply understand it.
True. But before using patterns we must have know how about it.:) Thanks and Regards:rose:
________________________________ Success is not something to wait for, its something to work for.
-
Many thanks for the valuable links. I'm still searching the book because its not available in the local market:(. Regards:rose:
________________________________ Success is not something to wait for, its something to work for.
-
When developing systems nowadays, it is very difficult to develop a system that doesn't have some forms of pattern applied to it. Developing applications is about good design and in the design process, you will discover what patterns apply.
the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer
Deja View - the feeling that you've seen this post before.Focus your design effort on the highest level business logic and unique requirements. 'Patterns' are a trap. Specifically, if you have some message coming in on your port, Your design will consist of a description of that message, and the action taken. Whether your code 'Polls' or uses 'Events' is irrelevant to this design. At one layer or another we are ALWAYS polling: These are your options: Write code that 'polls'. Use a library that polls on another thread and raises an event to your code. Use a library that uses lower level hardware that polls at an embedded level. Use a library, that uses hardware, that uses a chip that raises an interrupt as a result of the microprocessor 'polling' pins very quickly. If your highest level design is agnostic of 'design' patterns, then it is done right. It can be implemented successfully by any combination of language, or 'pattern'
-
Focus your design effort on the highest level business logic and unique requirements. 'Patterns' are a trap. Specifically, if you have some message coming in on your port, Your design will consist of a description of that message, and the action taken. Whether your code 'Polls' or uses 'Events' is irrelevant to this design. At one layer or another we are ALWAYS polling: These are your options: Write code that 'polls'. Use a library that polls on another thread and raises an event to your code. Use a library that uses lower level hardware that polls at an embedded level. Use a library, that uses hardware, that uses a chip that raises an interrupt as a result of the microprocessor 'polling' pins very quickly. If your highest level design is agnostic of 'design' patterns, then it is done right. It can be implemented successfully by any combination of language, or 'pattern'
Two things. Why are you replying on a very old comment? What relevance does polling have to do with the comment?