A pattern is simply a device used to skip out on costly dollars (as opposed
to cheap dollars). Software development is a low loyalties field. When new
workers come in and old ones are laid off, or when the project is complete
and you will likely not be working on the project again in the future,
Richard Quadling wrote:
2009/12/30 Tony Marston :
I have recently been engaged in an argument via email with someone who
criticises my low opinion of design patterns (refer to
http://www.tonymarston.net/php-mysql/design-patterns.html ). He says that
design patterns are merely a convention and no
2009/12/30 Tony Marston :
> I have recently been engaged in an argument via email with someone who
> criticises my low opinion of design patterns (refer to
> http://www.tonymarston.net/php-mysql/design-patterns.html ). He says that
> design patterns are merely a convention and not a reusable compon
I think it also to some extent comes down to having a shared
vocabulary. Pretty much the same way that you know which technique I'm
talking about when I use the word "recursion", which algorithm I'm
talking about when I say "quick sort" and which data structure I mean
when I say "linked list". It's
At 5:16 PM + 1/3/10, Tony Marston wrote:
I offer an alternative view - there are those programmers who need design
patterns to fill a hole in their experience, as a sort of mental crutch, and
there are those who do not need design patterns as they have the experience
and ability to work with
"Larry Garfield" wrote in message
news:201001010553.41956.la...@garfieldtech.com...
> On Friday 01 January 2010 05:26:48 am Tony Marston wrote:
>
>> > It depends what you're reusing. Design patterns are reusable concepts,
>> > not reusable code. That's the key difference.
>> >
>> > Knowledge o
On Friday 01 January 2010 05:26:48 am Tony Marston wrote:
> > It depends what you're reusing. Design patterns are reusable concepts,
> > not
> > reusable code. That's the key difference.
> >
> > Knowledge of design patterns is like knowledge of how different food
> > ingredients interact. "Hm,
"Larry Garfield" wrote in message
news:200912311743.16759.la...@garfieldtech.com...
> Meant to send this to the list, sorry.
>
> -- Forwarded Message --
>
> Subject: Re: [PHP] If design patterns are not supposed to produce reusable
> code then why u
Meant to send this to the list, sorry.
-- Forwarded Message --
Subject: Re: [PHP] If design patterns are not supposed to produce reusable
code then why use them?
Date: Thursday 31 December 2009
From: Larry Garfield
To: "Tony Marston"
On Wednesday 30 December 200
On Wed, Dec 30, 2009 at 04:50:40PM -, Tony Marston wrote:
> I have recently been engaged in an argument via email with someone who
> criticises my low opinion of design patterns (refer to
> http://www.tonymarston.net/php-mysql/design-patterns.html ). He says that
> design patterns are merely a
At 4:50 PM + 12/30/09, Tony Marston wrote:
What is your opinion? Are design patterns supposed to provide reusable code
or not? If not, and each implementation of a pattern takes just as much time
as the first, then where are the productivity gains from using design
patterns?
--
Tony Marston
On Wed, 2009-12-30 at 16:50 +, Tony Marston wrote:
> I have recently been engaged in an argument via email with someone who
> criticises my low opinion of design patterns (refer to
> http://www.tonymarston.net/php-mysql/design-patterns.html ). He says that
> design patterns are merely a con
I have recently been engaged in an argument via email with someone who
criticises my low opinion of design patterns (refer to
http://www.tonymarston.net/php-mysql/design-patterns.html ). He says that
design patterns are merely a convention and not a reusable component. My
argument is that somet
13 matches
Mail list logo