Comments on: Design Patterns as a statement of failure http://lesscode.org/2006/10/01/design-patterns-as-a-statement-of-failure/ AAaaaaahhhhrrrrrrr! Mon, 17 Sep 2007 09:10:42 +0000 http://wordpress.org/?v=2.0.1 by: Pianelli http://lesscode.org/2006/10/01/design-patterns-as-a-statement-of-failure/#comment-37879 Thu, 05 Apr 2007 22:03:10 +0000 http://lesscode.org/2006/10/01/design-patterns-as-a-statement-of-failure/#comment-37879 <p>I´m using Design Patterns in all on my projects written in PHP5. And I think you get your code more flexible than without design patterns.</p> I´m using Design Patterns in all on my projects written in PHP5. And I think you get your code more flexible than without design patterns.

]]> by: Trevor Baca http://lesscode.org/2006/10/01/design-patterns-as-a-statement-of-failure/#comment-17198 Fri, 27 Oct 2006 20:16:14 +0000 http://lesscode.org/2006/10/01/design-patterns-as-a-statement-of-failure/#comment-17198 <p>Couldn't agree with the quote from Mark more. I've been leading development work at two different development companies (NetworkIP and Jaduka.com) and at both companies we're just now finishing up a move from almost eight years of C into a brighter, newer future in python, neatly bypassing both Java and C++ for most of the significant server-side code in our projects. And what's been more important than anything -- especially with the move to python -- has been pattern agreement and understanding on our team. In general, we as programmers as a whole probably did need the intermediate state of enforced-OOP that Java and C++ provided. And it's nice that we're now able to apply patterns directly, regardless of langauge.</p> Couldn’t agree with the quote from Mark more. I’ve been leading development work at two different development companies (NetworkIP and Jaduka.com) and at both companies we’re just now finishing up a move from almost eight years of C into a brighter, newer future in python, neatly bypassing both Java and C++ for most of the significant server-side code in our projects. And what’s been more important than anything — especially with the move to python — has been pattern agreement and understanding on our team. In general, we as programmers as a whole probably did need the intermediate state of enforced-OOP that Java and C++ provided. And it’s nice that we’re now able to apply patterns directly, regardless of langauge.

]]> by: Danno http://lesscode.org/2006/10/01/design-patterns-as-a-statement-of-failure/#comment-14009 Sun, 01 Oct 2006 19:15:08 +0000 http://lesscode.org/2006/10/01/design-patterns-as-a-statement-of-failure/#comment-14009 <p>Holy guacamole! New lesscode articles!</p> <p>This one hits close to home for me. I'm taking a Generic Software Design class and I think they should change the name to "Exploring operations that have been done millions of times by people on C++ data types".</p> <p>Half of the time we keep revisiting the fact that an algorithm should have certain performance guarantees, but in practice, even in the GNU versions of the STL, there are performance violations. So, I'm like, "Well, christ, if we can't even get one of the most important distributions in the world to be well written, what hope does Joe Programmer have."</p> <p>Of course, I don't say that outloud because I don't want to fail the class, but I'm damned well thinking it.</p> Holy guacamole! New lesscode articles!

This one hits close to home for me. I’m taking a Generic Software Design class and I think they should change the name to “Exploring operations that have been done millions of times by people on C++ data types”.

Half of the time we keep revisiting the fact that an algorithm should have certain performance guarantees, but in practice, even in the GNU versions of the STL, there are performance violations. So, I’m like, “Well, christ, if we can’t even get one of the most important distributions in the world to be well written, what hope does Joe Programmer have.”

Of course, I don’t say that outloud because I don’t want to fail the class, but I’m damned well thinking it.

]]>