Comments on: Writing Modular Code - Overrides http://frankkoehl.com/2008/04/writing-modular-code-overrides/ The more you know, the more you don't know Wed, 19 Nov 2008 23:47:12 +0000 http://wordpress.org/?v=abc By: Frank http://frankkoehl.com/2008/04/writing-modular-code-overrides/#comment-16 Frank Wed, 28 May 2008 09:41:11 +0000 http://frankkoehl.com/?p=8#comment-16 @owen: I agree with you 100% that overrides play a huge part in frameworks, but why don't/can't they apply to modular code in general? If I'm writing homebrew, sans a framework, I can still put override logic in place so that other developers (or even my future self) can modify or extend my work with minimal effort. We hack code because we have to, but even homebrew code can be written to avoid this generally bad practice. @owen: I agree with you 100% that overrides play a huge part in frameworks, but why don’t/can’t they apply to modular code in general? If I’m writing homebrew, sans a framework, I can still put override logic in place so that other developers (or even my future self) can modify or extend my work with minimal effort. We hack code because we have to, but even homebrew code can be written to avoid this generally bad practice.

]]> By: owen http://frankkoehl.com/2008/04/writing-modular-code-overrides/#comment-15 owen Fri, 23 May 2008 15:11:07 +0000 http://frankkoehl.com/?p=8#comment-15 All of this is basically a howto on building a extension framework. you have function overrides, query overrides, onunload, before, after, when, listeners, observers, lookers, triggers, catches I look at this and I say why does this look like your writing a framework? overrides really have nothing to do with modular code. Modular code is for "simplicity" not "flexiblity". its important that you separate whats a "feature"/extension/option/"what if" from stuff thats actually a part of the software requirements. All of this is basically a howto on building a extension framework. you have function overrides, query overrides, onunload, before, after, when, listeners, observers, lookers, triggers, catches

I look at this and I say why does this look like your writing a framework? overrides really have nothing to do with modular code. Modular code is for “simplicity” not “flexiblity”. its important that you separate whats a “feature”/extension/option/”what if” from stuff thats actually a part of the software requirements.

]]> By: Mark http://frankkoehl.com/2008/04/writing-modular-code-overrides/#comment-6 Mark Fri, 11 Apr 2008 13:43:35 +0000 http://frankkoehl.com/?p=8#comment-6 Being able to articulate this is sometimes just as important as actually doing it to be able to kick it off. Nice post. Being able to articulate this is sometimes just as important as actually doing it to be able to kick it off. Nice post.

]]> By: Gary http://frankkoehl.com/2008/04/writing-modular-code-overrides/#comment-5 Gary Wed, 09 Apr 2008 14:27:21 +0000 http://frankkoehl.com/?p=8#comment-5 Daddy like.. Well done. Daddy like.. Well done.

]]>