Comments on: The Lazy, Clever Programmer: A Compendium Of Code Reuse & Recycling

By: Green development « OddCog.com

Green development « OddCog.com — Sat, 27 Jun 2009 11:23:19 +0000

[...] have just read a great article on code reuse. I always thought that the term DRY, as in Don’t Repeat Yourself, was missing something – [...]

By: bob-ak.com » Blog Archive » The Lazy, Clever Programmer: A Compendium Of Code Reuse & Recycling

Thu, 31 Jul 2008 10:48:22 +0000

[...] full post here Posted by bobak Filed in [...]

By: You Suck At Programming And I Hate You: Things NEVER To Do In PHP & SQL :: HTMList.com

Fri, 25 Jul 2008 09:13:26 +0000

[...] field is inserted at the end of the table. Completely stupid, that. There are smart ways to be a lazy programmer and idiotic ways. Guess which one this [...]

By: Andrew

Andrew — Sun, 20 Jul 2008 16:13:50 +0000

Over more than 9 years developing code one gets a sense of highly re-useable components. Loggers, Debuggers etc. I feel that not re-using code would cost me far more time that re-using as is components or event slightly adapting them. We know some things that happen over and over and get tools going for them like smarty for templating etc. I think its naieve to not think pf re-use as valuable and worth the time to document and built decent compnents themselves that lend themselves to re-use there has been plenty of times where under time constraints code re=use has saved my bacon as a coder in terms of getting a full project out and quickly.

By: links for 2008-07-20 « Mandarine

links for 2008-07-20 « Mandarine — Sun, 20 Jul 2008 04:39:16 +0000

[...] The Lazy, Clever Programmer: A Compendium Of Code Reuse & Recycling Recycling Aluminum, Plastic and Code. (tags: development webdev) [...]

By: Edgar Hassler

Edgar Hassler — Sun, 20 Jul 2008 02:40:51 +0000

pikine: Indeed, your namespacing solution is, in my opinion, the best way to make it valid. Over on Slashdot someone had other very good suggestions for forms. The other option that comes to mind is a two stage template like in PEAA, and convert these items to XHTML there. Either way, thanks for pointing out the concern for valid XHTML.

By: Edgar Hassler

Edgar Hassler — Sun, 20 Jul 2008 02:33:55 +0000

Unwesen: My choice to mention design patters was because they form a good taxonomic structure for discourse, and because they provide excellent hints at where to break apart various behaviors and states. When I look at a project and a component library, I find myself mapping things I want to do to design patterns implemented in (or supported by) the library so I may have gotten a little too loose with my vocabulary there. I agree with you completely that, just because something is built to patterns, does not mean it is reusable. In fact, forcing reuse of patternesque components can be traumatic to a project. Thanks for making that clear.

By: Edgar Hassler

Edgar Hassler — Sun, 20 Jul 2008 02:27:28 +0000

Hostyle: I think the power of javascript is that it’s easy to do validation, but consider presenting messages to the user (requiring themes for the messages) and preforming AJAX calls to submit forms (dealing with the different event orders can force you to merge unrelated actions). Further, with libraries the order of inclusion can cause problems. For example, if you include YUI before Yahoo Maps, Yahoo Maps will cause trouble in YUI events. One could use a solution like dojo’s but we’re working on minifying and delivering all libraries in one http transaction, so that wouldn’t work for us.

Understand that I did not intend to “rant” about javascript, in fact I like the language a lot and spend some of my spare time tinkering with a recursive descent parser for it. I hope you will continue to learn more about the language and its implementations, and choose to look for value in other people’s comments rather than dismissing them.

By: pikine

pikine — Sun, 20 Jul 2008 00:43:45 +0000

Sorry, your comment system ate my tag-like text, so I’m attempting again. (would be great to have a preview feature)

I thought that was a good idea until for some odd reason you need the output HTML to be standard compliant. Maybe xml namespace could come to the rescue, e.g. .

By: unwesen

unwesen — Sat, 19 Jul 2008 22:45:33 +0000

I’m not sure it was a good idea to mention design patterns here, to be honest. Many people confuse their intent a little (though reading through the article, I don’t think the author does).

Roughly speaking, design patterns are about implementing things “in this way”, as opposed to components, that implement things “in this place”.

So a design pattern is not necessarily a good candidate for a reusable component – though it can be. But most often it’s just a recipe for how to structure code that solves a single instance of a certain class of problems.

Picking up on the factory example given, you don’t want to create a factory for God objects…