Re: [PHP] Re: When to use design patterns?
At 8:50 PM -0600 2/24/08, Larry Garfield wrote: Design patterns are just that: A formalization of various common patterns that come up over and over in programming. Ever get the feeling wow, I know I've written something kinda like this at least three times now? That means it's probably a design pattern of some kind. Studying design patterns helps you recognize a give problem as being similar to another, so the solution is probably similar. It also can alert you to common pitfalls and common ways around them. I've read at least a couple of books on the subject and for something that's designed to make programming easier, I find it difficult to implement. I'm more like -- I've written something like this before -- I'm going to find my code and alter it -- type of guy. I'm sure it's my failing, but I program trees and not forest. From my perspective, you plant enough trees, the forest will take care of itself. Besides, every forest I've designed ends up a lot different than when I started. So I focus on trees -- it's simpler for me. I think it's good to develop a methodology so that you can reuse past code, but the design patterns' I've read about seem too abstract for me. Cheers, tedd -- --- http://sperling.com http://ancientstones.com http://earthstones.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: When to use design patterns?
Actually thats exactly what design patterns were created for. You come up with a basic structure and then modify it as needed for other projects. I mean, the objects/structures/whatever may change, but the patterns of logic you use will often be the same or only require minor adjustments. Its a whole lot better than trying to re-implement things again :) On Mon, Feb 25, 2008 at 9:20 AM, tedd [EMAIL PROTECTED] wrote: At 8:50 PM -0600 2/24/08, Larry Garfield wrote: Design patterns are just that: A formalization of various common patterns that come up over and over in programming. Ever get the feeling wow, I know I've written something kinda like this at least three times now? That means it's probably a design pattern of some kind. Studying design patterns helps you recognize a give problem as being similar to another, so the solution is probably similar. It also can alert you to common pitfalls and common ways around them. I've read at least a couple of books on the subject and for something that's designed to make programming easier, I find it difficult to implement. I'm more like -- I've written something like this before -- I'm going to find my code and alter it -- type of guy. I'm sure it's my failing, but I program trees and not forest. From my perspective, you plant enough trees, the forest will take care of itself. Besides, every forest I've designed ends up a lot different than when I started. So I focus on trees -- it's simpler for me. I think it's good to develop a methodology so that you can reuse past code, but the design patterns' I've read about seem too abstract for me. Cheers, tedd -- --- http://sperling.com http://ancientstones.com http://earthstones.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: When to use design patterns?
On Mon, Feb 25, 2008 at 9:20 AM, tedd [EMAIL PROTECTED] wrote: At 8:50 PM -0600 2/24/08, Larry Garfield wrote: Design patterns are just that: A formalization of various common patterns that come up over and over in programming. Ever get the feeling wow, I know I've written something kinda like this at least three times now? That means it's probably a design pattern of some kind. Studying design patterns helps you recognize a give problem as being similar to another, so the solution is probably similar. It also can alert you to common pitfalls and common ways around them. I've read at least a couple of books on the subject and for something that's designed to make programming easier, I find it difficult to implement. I'm more like -- I've written something like this before -- I'm going to find my code and alter it -- type of guy. I'm sure it's my failing, but I program trees and not forest. From my perspective, you plant enough trees, the forest will take care of itself. Besides, every forest I've designed ends up a lot different than when I started. So I focus on trees -- it's simpler for me. I think it's good to develop a methodology so that you can reuse past code, but the design patterns' I've read about seem too abstract for me. Cheers, tedd -- --- http://sperling.com http://ancientstones.com http://earthstones.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php To each their own I guess. Just out of curiosity, are you primarily writing entire web applications or one off scripts? I used to say you don't need all that but over time I just can't say it much anymore. It seems easy to just dive in and throw something out the door, but then new features need to be added. One of my favorite programming books, Design Patterns Explained, says Change happens! Deal with it. Using patterns helped me do just that with minimal crying because the underlying architecture could be easily modified. Also maybe look at Head First Design Patterns if you are interested in ever understanding them. Most of the books I've read say something along the lines of it should be obvious when to use these patterns when you read their book. This might be true for some/most people but I couldn't get my head wrapped around them till I read Head First. Seeing their examples with the fun writing just made things click for me. After reading that not only could I use them, but I started spotting them in peoples code. Another benefit of knowing patterns is having a common language for explaining solutions to problems between developers. Saying I'm using the decorator pattern makes much more sense then saying I'm wrapping this thing with another thing that makes it do something else so I can swap out behaviors because they work together, etc. ...but that is just the world I like to live in. :) -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: When to use design patterns?
On Mon, Feb 25, 2008 at 9:20 AM, tedd [EMAIL PROTECTED] wrote:
At 8:50 PM -0600 2/24/08, Larry Garfield wrote:
Design patterns are just that: A formalization of various common patterns
that
come up over and over in programming. Ever get the feeling wow, I know
I've
written something kinda like this at least three times now? That means
it's
probably a design pattern of some kind.
Studying design patterns helps you recognize a give problem as being
similar
to another, so the solution is probably similar. It also can alert you
to
common pitfalls and common ways around them.
I've read at least a couple of books on the subject and for something
that's designed to make programming easier, I find it difficult to
implement.
I'm more like -- I've written something like this before -- I'm
going to find my code and alter it -- type of guy.
I'm sure it's my failing, but I program trees and not forest. From my
perspective, you plant enough trees, the forest will take care of
itself. Besides, every forest I've designed ends up a lot different
than when I started. So I focus on trees -- it's simpler for me.
I think it's good to develop a methodology so that you can reuse past
code, but the design patterns' I've read about seem too abstract for
me.
some of the design patterns are a bit hard to grasp; and even harder to
determine when one might be appropriate to use. i think a common
misconception about people who advocate design patterns is that said
people attempt to use them arbitrarily. while this is undoubtedly true for
some people, design patterns are like anything else; mastery comes
through practice, and practice can be prone to errors.
that said, design patterns are mainly for adding layers of indirection, to
increase flexibility for an exchange of complexity and often times runtime
performance.
and also, there are patterns that are so trivial im sure weve all used them;
even tedd ;) for example, adapter, yes this is the famous, put a square peg
in a round hole pattern, but in reality its very simple,
/// NOTE: contrived example for demonstration only
function origFunction($p1, $p2, $p3) {}
function newFunction($p1, $p2) {
// pass the same thing for $p3 always for the new 'api'
return origFunction($p1, $p2, true);
}
another thing you will encounter studying patterns is subtle differences.
the non-patterns guys will call newFunction above, a 'wrapper'; and while
it is indeed that, 'wrapper' is a generic term. patterns have several types
of wrappers, adapter, decorator, proxy (and more im sure), which all have
different intents. Which brings us to one of the most important aspects of
patterns, a common vocabulary. this is an incredible tool that fosters
communication and enhanced efficiency.
take it or leave it; i think patterns are worth while.
-nathan
Re: [PHP] Re: When to use design patterns?
I agree, that head first book is fantabulous. Very well written and easy to read for a techie book. It makes the usage of design patterns incredibly easy to understand. But like all things simply understanding the theory doesn't always equal being able to practice it... that only comes with using them. On Mon, Feb 25, 2008 at 9:51 AM, Eric Butera [EMAIL PROTECTED] wrote: On Mon, Feb 25, 2008 at 9:20 AM, tedd [EMAIL PROTECTED] wrote: At 8:50 PM -0600 2/24/08, Larry Garfield wrote: Design patterns are just that: A formalization of various common patterns that come up over and over in programming. Ever get the feeling wow, I know I've written something kinda like this at least three times now? That means it's probably a design pattern of some kind. Studying design patterns helps you recognize a give problem as being similar to another, so the solution is probably similar. It also can alert you to common pitfalls and common ways around them. I've read at least a couple of books on the subject and for something that's designed to make programming easier, I find it difficult to implement. I'm more like -- I've written something like this before -- I'm going to find my code and alter it -- type of guy. I'm sure it's my failing, but I program trees and not forest. From my perspective, you plant enough trees, the forest will take care of itself. Besides, every forest I've designed ends up a lot different than when I started. So I focus on trees -- it's simpler for me. I think it's good to develop a methodology so that you can reuse past code, but the design patterns' I've read about seem too abstract for me. Cheers, tedd -- --- http://sperling.com http://ancientstones.com http://earthstones.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php To each their own I guess. Just out of curiosity, are you primarily writing entire web applications or one off scripts? I used to say you don't need all that but over time I just can't say it much anymore. It seems easy to just dive in and throw something out the door, but then new features need to be added. One of my favorite programming books, Design Patterns Explained, says Change happens! Deal with it. Using patterns helped me do just that with minimal crying because the underlying architecture could be easily modified. Also maybe look at Head First Design Patterns if you are interested in ever understanding them. Most of the books I've read say something along the lines of it should be obvious when to use these patterns when you read their book. This might be true for some/most people but I couldn't get my head wrapped around them till I read Head First. Seeing their examples with the fun writing just made things click for me. After reading that not only could I use them, but I started spotting them in peoples code. Another benefit of knowing patterns is having a common language for explaining solutions to problems between developers. Saying I'm using the decorator pattern makes much more sense then saying I'm wrapping this thing with another thing that makes it do something else so I can swap out behaviors because they work together, etc. ...but that is just the world I like to live in. :) -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: When to use design patterns?
My favourite patterns are the following: factory singleton adaptor These also happen to be the most common I come across. Cheers, Rob. On Mon, 2008-02-25 at 10:31 -0500, Matty Sarro wrote: I agree, that head first book is fantabulous. Very well written and easy to read for a techie book. It makes the usage of design patterns incredibly easy to understand. But like all things simply understanding the theory doesn't always equal being able to practice it... that only comes with using them. On Mon, Feb 25, 2008 at 9:51 AM, Eric Butera [EMAIL PROTECTED] wrote: On Mon, Feb 25, 2008 at 9:20 AM, tedd [EMAIL PROTECTED] wrote: At 8:50 PM -0600 2/24/08, Larry Garfield wrote: Design patterns are just that: A formalization of various common patterns that come up over and over in programming. Ever get the feeling wow, I know I've written something kinda like this at least three times now? That means it's probably a design pattern of some kind. Studying design patterns helps you recognize a give problem as being similar to another, so the solution is probably similar. It also can alert you to common pitfalls and common ways around them. I've read at least a couple of books on the subject and for something that's designed to make programming easier, I find it difficult to implement. I'm more like -- I've written something like this before -- I'm going to find my code and alter it -- type of guy. I'm sure it's my failing, but I program trees and not forest. From my perspective, you plant enough trees, the forest will take care of itself. Besides, every forest I've designed ends up a lot different than when I started. So I focus on trees -- it's simpler for me. I think it's good to develop a methodology so that you can reuse past code, but the design patterns' I've read about seem too abstract for me. Cheers, tedd -- --- http://sperling.com http://ancientstones.com http://earthstones.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php To each their own I guess. Just out of curiosity, are you primarily writing entire web applications or one off scripts? I used to say you don't need all that but over time I just can't say it much anymore. It seems easy to just dive in and throw something out the door, but then new features need to be added. One of my favorite programming books, Design Patterns Explained, says Change happens! Deal with it. Using patterns helped me do just that with minimal crying because the underlying architecture could be easily modified. Also maybe look at Head First Design Patterns if you are interested in ever understanding them. Most of the books I've read say something along the lines of it should be obvious when to use these patterns when you read their book. This might be true for some/most people but I couldn't get my head wrapped around them till I read Head First. Seeing their examples with the fun writing just made things click for me. After reading that not only could I use them, but I started spotting them in peoples code. Another benefit of knowing patterns is having a common language for explaining solutions to problems between developers. Saying I'm using the decorator pattern makes much more sense then saying I'm wrapping this thing with another thing that makes it do something else so I can swap out behaviors because they work together, etc. ...but that is just the world I like to live in. :) -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- .. | InterJinn Application Framework - http://www.interjinn.com | :: | An application and templating framework for PHP. Boasting | | a powerful, scalable system for accessing system services | | such as forms, properties, sessions, and caches. InterJinn | | also provides an extremely flexible architecture for | | creating re-usable components quickly and easily. | `' -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: When to use design patterns?
On Mon, Feb 25, 2008 at 10:38 AM, Robert Cummings [EMAIL PROTECTED] wrote: My favourite patterns are the following: factory singleton adaptor i dont know about any favorites at this time but as far as common, id say strategy adapter template method (often used in conjunction w/ factory) singleton too (watch out for eric; hes a registry guy ;)) (and this is the top 3 from my exp list so had to stuff singleton by the wayside :)) the heads first book is key ;) and also, you might check out phppatterns.com; though it hasnt been updated in a while id consider it somewhat of a classic source on patterns w/ php as the example language. -nathan
Re: [PHP] Re: When to use design patterns?
tedd wrote: At 8:50 PM -0600 2/24/08, Larry Garfield wrote: Design patterns are just that: A formalization of various common patterns that come up over and over in programming. Ever get the feeling wow, I know I've written something kinda like this at least three times now? That means it's probably a design pattern of some kind. Studying design patterns helps you recognize a give problem as being similar to another, so the solution is probably similar. It also can alert you to common pitfalls and common ways around them. I've read at least a couple of books on the subject and for something that's designed to make programming easier, I find it difficult to implement. I'm more like -- I've written something like this before -- I'm going to find my code and alter it -- type of guy. I'm sure it's my failing, but I program trees and not forest. From my perspective, you plant enough trees, the forest will take care of itself. Besides, every forest I've designed ends up a lot different than when I started. So I focus on trees -- it's simpler for me. Not to say that what you are doing is wrong, but we had a guy here in our office that was/is a cut/paste master. If he had a routine that he found that (almost) worked. He would then use that same chunk of code everywhere. But, if that same bit of code got almost the right answer, he would write a fix that would get it right this time. Then the next time he used the re-written code, he would have to write another fix. This went on for two years. When they brought me in to take over managing his code, I re-wrote the entire lib in one weekend. I have not had to touch the base code since then, and it is right every time. It is much lighter and faster. The moral of my story, you keep adding floors to your sky riser, the foundation is not going to support the add structure. Build yourself a re-enforced foundation, you will never have to worry about how many floors you have to put on top of it. All you will need to do is build yourself a structure that deals with the results returned to you by your base code. The other day I gave an example of how I use code: Users::GetGroup($somegroup)-update(); And I got this response It really sucks for debugging though, because what if GetGroup($somegroup) returns a null or unexpected value? The idea is, if you wrote the code, then you force it to return to you what you want. In this case, if something went wrong in the GetGroup() static method, the I would return my normal object that has the update() method, at the same time I would create an exception and catch that upstream. Probably a little long winded on this one and maybe a little off this topic. Sorry. I think it's good to develop a methodology so that you can reuse past code, but the design patterns' I've read about seem too abstract for me. Cheers, tedd -- Jim Lucas Some men are born to greatness, some achieve greatness, and some have greatness thrust upon them. Twelfth Night, Act II, Scene V by William Shakespeare -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: When to use design patterns?
On Mon, Feb 25, 2008 at 11:07 AM, Nathan Nobbe [EMAIL PROTECTED] wrote: On Mon, Feb 25, 2008 at 10:38 AM, Robert Cummings [EMAIL PROTECTED] wrote: My favourite patterns are the following: factory singleton adaptor i dont know about any favorites at this time but as far as common, id say strategy adapter template method (often used in conjunction w/ factory) singleton too (watch out for eric; hes a registry guy ;)) (and this is the top 3 from my exp list so had to stuff singleton by the wayside :)) the heads first book is key ;) and also, you might check out phppatterns.com; though it hasnt been updated in a while id consider it somewhat of a classic source on patterns w/ php as the example language. -nathan I'm not going to even say anything. :) Since we're declaring our love for specifics, I really like the observer pattern lately for adding a way to add features without touching the core. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: When to use design patterns?
On Mon, Feb 25, 2008 at 12:06 PM, Eric Butera [EMAIL PROTECTED] wrote: I'm not going to even say anything. :) Since we're declaring our love for specifics, I really like the observer pattern lately for adding a way to add features without touching the core. ahh yes, observer is key; i cant believe i forgot it! -nathan
RE: [PHP] Re: When to use design patterns?
[snip] Design patterns are used to solve common problems to in OOP programming. [/snip] It is just not limited to OOP, design patterns are used to solve common programming problems regardless of methodology. They have come into vogue with OOP and have been leveraged heavily in that case. Design patterns are everywhere. Do you need to use them? Only if the case implies it. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: When to use design patterns?
At 10:31 AM -0500 2/25/08, Matty Sarro wrote: Also maybe look at Head First Design Patterns if you are interested in ever understanding them. Okay -- thanks for the recommendation -- I just bought it. Cheers, tedd -- --- http://sperling.com http://ancientstones.com http://earthstones.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: When to use design patterns?
At 9:51 AM -0500 2/25/08, Eric Butera wrote: To each their own I guess. Just out of curiosity, are you primarily writing entire web applications or one off scripts? If a client can describe it, that's what I do. As compared to some of the others of this list, I'm just a script-kiddy. But, I do have the ability to make just about anything work AND look good! So we all have our place. I do everything from basic design to back-end stuff and everything in between -- all with the newest buzz-words applied (i.e., graceful degradation, unobtrusive code, accessible, functional, secure, and it validates). My clients seem pleased, I love the work, and I get paid. I program 10 to 14 hours per day and 6 to 7 days per week. So even someone as limited as me, will learn something from that work load. I would like to think I'm an agile programmer. But the truth is, I survive in constantly changing technology. Does that answer your question? Cheers, tedd -- --- http://sperling.com http://ancientstones.com http://earthstones.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: When to use design patterns?
On Feb 25, 2008, at 4:18 PM, tedd wrote: At 9:51 AM -0500 2/25/08, Eric Butera wrote: To each their own I guess. Just out of curiosity, are you primarily writing entire web applications or one off scripts? If a client can describe it, that's what I do. As compared to some of the others of this list, I'm just a script- kiddy. But, I do have the ability to make just about anything work AND look good! So we all have our place. I do everything from basic design to back-end stuff and everything in between -- all with the newest buzz-words applied (i.e., graceful degradation, unobtrusive code, accessible, functional, secure, and it validates). Can you do web 2.0? Because it just HAS to be web 2.0... anything else is s last version :) -- Jason Pruim Raoset Inc. Technology Manager MQC Specialist 3251 132nd ave Holland, MI, 49424-9337 www.raoset.com [EMAIL PROTECTED] -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: When to use design patterns?
Can you do web 2.0? Because it just HAS to be web 2.0... anything else is s last version :) Yuck - I hate overuse of 'web 2.0' stuff. Don't add features that don't benefit your users and if you must do fancy stuff then please make sure your site still works for users without Javascript, Flash, Java, etc. I've been fighting with stupid Joomla lately because it throws Javascript errors making it unusable. smime.p7s Description: S/MIME Cryptographic Signature
Re: [PHP] Re: When to use design patterns?
Dangit, I can only do web1.9.5 :( I guess I've been deprecated... On Mon, Feb 25, 2008 at 4:27 PM, Jason Pruim [EMAIL PROTECTED] wrote: On Feb 25, 2008, at 4:18 PM, tedd wrote: At 9:51 AM -0500 2/25/08, Eric Butera wrote: To each their own I guess. Just out of curiosity, are you primarily writing entire web applications or one off scripts? If a client can describe it, that's what I do. As compared to some of the others of this list, I'm just a script- kiddy. But, I do have the ability to make just about anything work AND look good! So we all have our place. I do everything from basic design to back-end stuff and everything in between -- all with the newest buzz-words applied (i.e., graceful degradation, unobtrusive code, accessible, functional, secure, and it validates). Can you do web 2.0? Because it just HAS to be web 2.0... anything else is s last version :) -- Jason Pruim Raoset Inc. Technology Manager MQC Specialist 3251 132nd ave Holland, MI, 49424-9337 www.raoset.com [EMAIL PROTECTED] -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: When to use design patterns?
On 2/25/08, Michael McGlothlin [EMAIL PROTECTED] wrote: I've been fighting with stupid Joomla lately because it throws Javascript errors making it unusable. The un-usability began for me when I became aware of the 250+ published exploits under it's current Joomla name: http://search.securityfocus.com/swsearch?query=joomlametaname=alldoc And the 280+ exploits when it was called Mambo: http://search.securityfocus.com/swsearch?query=mambometaname=alldoc -- Greg Donald http://destiney.com/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: When to use design patterns?
Greg Donald wrote: On 2/25/08, Michael McGlothlin [EMAIL PROTECTED] wrote: I've been fighting with stupid Joomla lately because it throws Javascript errors making it unusable. The un-usability began for me when I became aware of the 250+ published exploits under it's current Joomla name: http://search.securityfocus.com/swsearch?query=joomlametaname=alldoc And the 280+ exploits when it was called Mambo: http://search.securityfocus.com/swsearch?query=mambometaname=alldoc Not disagreeing with you, but just to be clear Joomla is a fork of Mambo, not a rename. -Stut -- http://stut.net/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: When to use design patterns?
On Mon, 2008-02-25 at 16:35 -0500, Matty Sarro wrote: Dangit, I can only do web1.9.5 :( I guess I've been deprecated... Loozers... I come from the year 3129 and we do DWeb 80.3 on the Hyperweb! We can link to the past... we found Zelda! *groan :)* Cheers, Rob. -- .. | InterJinn Application Framework - http://www.interjinn.com | :: | An application and templating framework for PHP. Boasting | | a powerful, scalable system for accessing system services | | such as forms, properties, sessions, and caches. InterJinn | | also provides an extremely flexible architecture for | | creating re-usable components quickly and easily. | `' -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: When to use design patterns?
At 4:27 PM -0500 2/25/08, Jason Pruim wrote: On Feb 25, 2008, at 4:18 PM, tedd wrote: I do everything from basic design to back-end stuff and everything in between -- all with the newest buzz-words applied (i.e., graceful degradation, unobtrusive code, accessible, functional, secure, and it validates). Can you do web 2.0? Because it just HAS to be web 2.0... anything else is s last version :) No, I'm already doing Web 3.0. In this biz, you have to stay ahead of the game. Cheers, tedd -- --- http://sperling.com http://ancientstones.com http://earthstones.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: When to use design patterns?
At 9:58 PM + 2/25/08, Stut wrote: Not disagreeing with you, but just to be clear Joomla is a fork of Mambo. -Stut Oh, I thought everyone was talking about dances and all along it's been silverware. Damn, I'm never going to get this design pattern thing. :-) Cheers, tedd -- -- http://sperling.com http://ancientstones.com http://earthstones.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] Re: When to use design patterns?
carlos wrote: skylark wrote: Design patterns are really hot today. And I am really interested when and how often they are used. It is said that 99% of the projects don't need them. Design patterns are used to solve common problems to in OOP programming. If you use OOP, chances are you have used a design pattern without even being aware of it. I like to make the right hand side of all my code look like a contemporary ascii art vase. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: When to use design patterns?
On Saturday 23 February 2008, carlos wrote: skylark wrote: Design patterns are really hot today. And I am really interested when and how often they are used. It is said that 99% of the projects don't need them. Design patterns are used to solve common problems to in OOP programming. If you use OOP, chances are you have used a design pattern without even being aware of it. Untrue. Design patterns are not OOP-specific, although they are frequently discussed in OOP terms. Design patterns are just that: A formalization of various common patterns that come up over and over in programming. Ever get the feeling wow, I know I've written something kinda like this at least three times now? That means it's probably a design pattern of some kind. Studying design patterns helps you recognize a give problem as being similar to another, so the solution is probably similar. It also can alert you to common pitfalls and common ways around them. -- Larry Garfield AIM: LOLG42 [EMAIL PROTECTED] ICQ: 6817012 If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it. -- Thomas Jefferson -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] Re: When to use design patterns?
skylark wrote: Design patterns are really hot today. And I am really interested when and how often they are used. It is said that 99% of the projects don't need them. Design patterns are used to solve common problems to in OOP programming. If you use OOP, chances are you have used a design pattern without even being aware of it. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
