I’m presenting at the CF in NC conference in October

I am super excited to announce that I’ve been selected to present a session at the CF in NC conference in Raleigh, NC in October. This will be my first time presenting to a conference setting and I am really looking forward to the experience. Just last week I gave my first ever technical presentation to the CFMeetup group and got some great feedback.

I’ll be presenting an introduction to dependency injection using the ColdSpring framework titled “Intro to ColdSpring: A solution to a problem you may not know you have”.

I’m also looking forward to meeting face-to-face with a bunch of folks I’ve interacted with digitally over the last few years. Hope to see a bunch of you there!

Followup to my CFMeetup development environment presentation

Last week I gave a presentation to the CFMeetup group showing how I use Eclipse and Tomcat to develop CFML applications across any of the current CFML engines (if you missed it and are interested, here is the link to the meeting recording). One of the aspects of my environment that we didn’t have time to discuss is the link between the Apache web server and Tomcat. Some people will accurately point out that you don’t really need the Apache web server since Tomcat has a very fast built-in server that you can easily configure to run on port 80 rather than the default 8080. I personally like to try to keep things as close to production configurations as possible so I use the Apache web server when developing locally.

Read More

Speaking to the CFMeetup group on August 20

Charlie Arehart posted this to the CFMeetup site this morning so I thought I’d announce it here too. I will be speaking to the CFMeetup group on Thursday, August 20th at 12:00pm ET. We are going to be talking about one way to set up a development environment for ColdFusion application development that will use Eclipse 3.5 and Tomcat 6 to allow you to develop your applications against any of the major CFML server engines out there today.

This will be my first CFMeetup presentation and I’m both nervous and excited.

The link for the CFMeetup is http://www.meetup.com/coldfusionmeetup/calendar/11128508/.

UPDATE: I’ve attached the slides and XML snippet that I referenced in the presentation. The URL for the recording is http://experts.na3.acrobat.com/p39094247/. Thanks to everyone for attending and for all the feedback.

Using the new HTMLHelperProperty in MachII 1.8

I ran into a situation this week while working on a MachII project I’m doing with my brother that I’m sure many of you have encountered before. We have our view pages broken up into small chunks that we render inside a “pod-like” layout on the screen. Many of these view pages are using a one or more jQuery plugins (including cfUniform, DataTables and FancyBox) which need the main jQuery library to be included in the header to make them work correctly. We had been doing something like this in the top of each view that needed jQuery:

1
2
3
4
5
6
<cfsavecontent variable="jQueryInit">
     <script type="text/javascript" language="javascript"
         src="/javascript/jquery-1.3.2.min.js"></script>
</cfsavecontent>
 
<cfhtmlhead text="#jQueryInit#"></cfhtmlhead>

This worked perfectly fine for a while, right up until the point where we had two views in the same request that needed jQuery. If you put the above code in each of the view pages, then only some of your jQuery plugins work because the jQuery javascript file was getting loaded and instantiated multiple times–wiping out everything that had been configured previously.

Read More

There is no such thing as perfect code

The title alone may offend some folks that read this post, but, please, hear me out before you close the browser window and go away muttering “this guy has no idea what he’s talking about”. I was talking to a developer friend of mine today and he made the statement “there is no such thing as perfect code”. The statement kind of took me by surprise but as we talked through it, I came to see his particular point.

How many times have you written an application or feature that solved a particular problem and then gone back to look at it later and thought to yourself “this is some really crappy code that I wrote–I wish I could redo this and do it ‘right'”? I know I have had that thought countless times looking at things I’ve written over the last 11 years of my professional development career. Did we think the code was “crappy” when we launched the application? Chances are the answer at that time was no. So, what changed?

Read More