We had a great time Friday night with around 170 in attendance! Terry did a great job and everyone left hungry for the new releases that he teased. Here are some pics from the night.
I recently put a job posting out to my CFUG for an on-site Jr-Mid level ColdFusion developer in the DFW area and have had no luck at all. The only responses I have received are either from overqualified developers who were already engaged and just sniffing around, or people out of the area that wanted to work remotely. Many of the replies on the email list were from other people that had posted jobs previously and were making comments that they too were having a hard time filling spots. What a different time for ColdFusion developers today than it was a few short years ago!
But as nice as those implications are for us…. I need a developer now!
I am giving a presentation to my CFUG tonight demonstrating a method of writing your code in a way that will support multiple data persistence methods. In the example code, there is a mini-app that adds/edits/deletes addresses from the following storage methods: 1) MSSQL using Stored Procs, 2) MySQL using straight SQL, and 3) encrypted WDDX text files. The approach uses subclasses of the AddressDao and AddressGateway that are specific to the type of storage. Below is the blurb from the www.dfwcfug.com site:
Dave Shuck: Subclassing Data Components for Flexible Applications
One of the advantages that you hear repeatedly of a good OO design, using DAO and Gateway patterns is the database abstraction. One benefit of database abstraction is that your application is not tied to a specific database architecture. This means that if you suddenly need to uproot your site and move to a different database, you do not have countless queries buried throughout your code. If you followed the rules and followed the patterns, then you simply need to alter the code that persists your data in the DAO and Gateway objects. But what if you are building an application that you know will sit on several different databases or use different methods for data persistence? One method would be to create subclasses of your DAOs and Gateways that deal with specific persistence needs. I will be showing a simple example mini-application I wrote that will demonstrate how the database has a somewhat insignificant role in an OO system. We will be running the same code on top of three data persistence methods: 1) MS SQL with stored procedures, 2) MySQL with plain SQL, and 3) Encrypted WDDX text files (Why? Because we can!).