ColdFuision is a dynamic scripting language. You've probably heard that over and over again but you may not realize just how much power that gives you over languages like Java. This presentation takes a whirlwind tour of several advanced techniques that are only possible in a dynamic language. The only place this presentation has ever been given is Scotch 2008 where it was met with complete and utter bewilderment!

Subtitled: Building services with ColdSpring and Transfer. This presentation looks at my experiences creating a Service Oriented Architecture for the Adobe Hosted Services team (the Software as a Service group behind Kuler, Share and so on). The presentation introduces SOA concepts, how they map to ColdFusion, what changes when you write remote APIs for non-ColdFusion clients, what worked and what didn't. Originally given at cf.Objective() 2007 I believe.

We're starting to see a lot of interest in event-driven programming because Flex demands it, AJAX uses it to some extent and some popular application frameworks use this approach (ColdBox, Mach-II, Model-Glue). This talks looks at expanding this technique to other aspects of ColdFusion programming. If Flex looks alien to you, this talk should let you get your head around the techniques in a familiar environment, helping you get ready for Flex. This is the updated version that was given at MAX 2008 which has a different focus in several examples and a different flow through the deck.

We're starting to see a lot of interest in event-driven programming because Flex demands it, AJAX uses it to some extent and some popular application frameworks use this approach (ColdBox, Mach-II, Model-Glue). This talks looks at expanding this technique to other aspects of ColdFusion programming. If Flex looks alien to you, this talk should let you get your head around the techniques in a familiar environment, helping you get ready for Flex. This is the version from CFUnited 2008. An updated version was given at MAX 2008.

The original 2004(?) version of this presentation that compares Mach-II, Model-Glue and Fusebox. It focuses heavily on Fusebox since that supports several styles of development. A recent version of this presentation will be available soon that compares ColdBox as well.

This presentation provides an overview of "modern" Fusebox with the first preview of Fusebox 5.5 features. It loses a lot without the demos.

We're used to the XML language of application frameworks being a static, fixed thing. If it doesn't let you do what you want, you're out of luck. Not so with Fusebox 5! This recent release lets you define your own verbs, which offers a much richer, more expressive way to build applications. This session will briefly walk you through the architecture of Fusebox and then dive into how to use third party custom lexicons as well as how to write your own language extensions. Enjoy the power of higher-level abstractions without the performance penalties they so often bring! From Frameworks 2007.

The conventional wisdom for working with CFCs is that you should provide returntypes and argument types for methods. This idea stems from working with strongly-typed languages such as Java and C#. What if, though, we accepted ColdFusion as a dynamically-typed language, such as Smalltalk or Ruby? This talk explores the problems "duck typing" solves and the new possibilities it opens. This is an updated version from 2008 when I presented to BACFUG.

The conventional wisdom for working with CFCs is that you should provide returntypes and argument types for methods. This idea stems from working with strongly-typed languages such as Java and C#. What if, though, we accepted ColdFusion as a dynamically-typed language, such as Smalltalk or Ruby? This talk explores the problems "duck typing" solves and the new possibilities it opens. This is the original version from CFUnited 2006 when I replaced Hal Helms at very short notice!

Come find out what design patterns are really about and how they can make your life easier. (You're probably already using some design patterns, although you may not know it.) For this session, we have distilled decades of software engineering experience into a well- documented set of blueprints that can be applied to common problems to ensure clean, maintainable code.This appeared in several similar versions. I think this is the December 2007 version from CFMeetUp?