Comments on: ColdFusion and Design Patterns http://www.simonwhatley.co.uk/coldfusion-and-design-patterns The opposite of every great idea is another great idea Thu, 28 Aug 2008 17:18:18 +0000 http://wordpress.org/?v=2.6.1 By: Simon http://www.simonwhatley.co.uk/coldfusion-and-design-patterns#comment-2831 Simon Tue, 07 Aug 2007 13:04:25 +0000 http://www.simonwhatley.co.uk/coldfusion-and-design-patterns#comment-2831 @George. I will try and address the use of beans, DAOs, Gateways and Facade in upcoming posts. @Jared. I certainly agree with your statement regarding poorly written code. An inherent weekness in any code is the developer used to create the application. This is and area ColdFusion junkies need to address as on so may occassions I get people, largely ignorant of ColdFusion, belittling it due to poor specifications and architecture. Although there is a section of developers out there using good practice, there is also a large, if not dominant, number who do not. @George. I will try and address the use of beans, DAOs, Gateways and Facade in upcoming posts.

@Jared. I certainly agree with your statement regarding poorly written code. An inherent weekness in any code is the developer used to create the application. This is and area ColdFusion junkies need to address as on so may occassions I get people, largely ignorant of ColdFusion, belittling it due to poor specifications and architecture. Although there is a section of developers out there using good practice, there is also a large, if not dominant, number who do not.

]]> By: Jared Rypka-Hauer http://www.simonwhatley.co.uk/coldfusion-and-design-patterns#comment-2829 Jared Rypka-Hauer Mon, 06 Aug 2007 01:18:04 +0000 http://www.simonwhatley.co.uk/coldfusion-and-design-patterns#comment-2829 Simon, I like the idea, which is basically getting people to think about what they're doing so that what they produce is balanced between maintainability, performance, and cost. In fairness, though, there's a couple things I'd like to disagree with, too. ;) First, ColdFusion still, to this very day, allows for poorly-written software, as does pretty much every programming language from the 8,000 that exist. You can be thoughtful or not when developing software and, as a result, write well or write poorly. No language prevents people from doing a poor job, just as no tool prevents a carpenter from doing a poor job. Second, the shift may be growing larger, but people have been producing well-written and even pattern-based software for years with CF. I'm only noting this to be fair to them. It's not like everything put out by the CF community in the first 7 of the last 10 years was poorly done. A lot of it is encapsulated, reusable code that does its job well. And that brings me to my final point... things like Fusebox, the ColdFusion Extension API for C++ (CFX), and custom tags are overlooked (in an historical context, anyway) as tools that allowed developers to build software based on either design patterns or architectural patterns. Granted they have become more mature lately and many of us have helped spread the word about MVC and OO and so on, but even way back in the summer of 99, we had some of this stuff available to us. All in all a good post, and I want to be clear that I'm just trying to contribute to a larger and very important conversation here. ;) Thanks, J Simon,

I like the idea, which is basically getting people to think about what they’re doing so that what they produce is balanced between maintainability, performance, and cost.

In fairness, though, there’s a couple things I’d like to disagree with, too. ;) First, ColdFusion still, to this very day, allows for poorly-written software, as does pretty much every programming language from the 8,000 that exist. You can be thoughtful or not when developing software and, as a result, write well or write poorly. No language prevents people from doing a poor job, just as no tool prevents a carpenter from doing a poor job.

Second, the shift may be growing larger, but people have been producing well-written and even pattern-based software for years with CF. I’m only noting this to be fair to them. It’s not like everything put out by the CF community in the first 7 of the last 10 years was poorly done. A lot of it is encapsulated, reusable code that does its job well.

And that brings me to my final point… things like Fusebox, the ColdFusion Extension API for C++ (CFX), and custom tags are overlooked (in an historical context, anyway) as tools that allowed developers to build software based on either design patterns or architectural patterns. Granted they have become more mature lately and many of us have helped spread the word about MVC and OO and so on, but even way back in the summer of 99, we had some of this stuff available to us.

All in all a good post, and I want to be clear that I’m just trying to contribute to a larger and very important conversation here. ;)

Thanks,
J

]]> By: Michael White http://www.simonwhatley.co.uk/coldfusion-and-design-patterns#comment-2828 Michael White Sun, 05 Aug 2007 23:25:52 +0000 http://www.simonwhatley.co.uk/coldfusion-and-design-patterns#comment-2828 I am trying to adapt my coding from pseudo-OO to real OO and looking for a good explaination, example of how beans and dao and gateways all interact, and about facade patterns and how they can be used to allow you to better separate your user interface from all the back end logic. I am trying to adapt my coding from pseudo-OO to real OO and looking for a good explaination, example of how beans and dao and gateways all interact, and about facade patterns and how they can be used to allow you to better separate your user interface from all the back end logic.

]]> By: George Bridgeman http://www.simonwhatley.co.uk/coldfusion-and-design-patterns#comment-2827 George Bridgeman Sun, 05 Aug 2007 14:04:51 +0000 http://www.simonwhatley.co.uk/coldfusion-and-design-patterns#comment-2827 Another good design patterns book: Patterns of Enterprise Application Architecture. By Martin Fowler. ISBN 0-321-12742-0. Still working my way through it so can't give a decent review but enjoying it so far. Another good design patterns book: Patterns of Enterprise Application Architecture. By Martin Fowler. ISBN 0-321-12742-0. Still working my way through it so can’t give a decent review but enjoying it so far.

]]>