I make no comment for fear of retribution. Check it out and decide for yourself.

The demon cat will get you

Just updated to blogCFC 5.7. The update was painless, and I really like the new pod manager. Thanks, Ray, for the foresight to keep all of the pods showing if none have been selected. I'm using Rob Rohan's Afae Blogger to write this blog, and one of the few issues I had with it was that I had to close and refresh the Entries list in order to load the entry back from the site. With the new blogCFC update, this issue seems to be fixed. Thanks to both Ray Camden and Rob Rohan for the great tools!

I just watched Ray Camden's breeze presentation on Application.cfc. Since most of the apps I have been working on for the past couple of years (at my paying job) have been on CF 6.1, I haven't had the need to really explore the uses of Application.cfc. This will be changing soon, so I figured that it would be a good idea to get up to speed. Ray's presentation is very good, and I recommend it to anyone that needs to learn about this topic, and also to anyone that just needs a refresher.

This post is in response to Nathan Mische's post on Perforce. I've been using Perforce for about four years, and during that time, I've developed a real love/hate relationship with this amazing and annoying tool. Perhaps I should explain...

Amazing

Whatever kind of project you are working on, Perforce can accomodate it. Got a simple website? No problem. Just drag the site folder into Perforce and it's instantly added to version control. Even better, the gang at Perforce have put together an amazing plugin for Eclipse that allows you to handle almost all of your normal workflow without leaving Eclipse. By far, my favorite feature in Perforce is the way is handles branching (integration in Perforce-speak). Let's pretend for a moment that you work for a company that uses multiple environments: Development, Testing, Staging, Production. And further, your imaginary company also has to deal with auditing, validation, Sarbanes-Oxley, etc. This means that you can't just copy your code from one environment to another as you please. Every change must be tracked and logged. With Perforce, such auding is easy. Just set up branches for each of your environments. When you need to promote code (from staging to production, for example), all you need to do is tell Perforce to integrate from the Staging branch to the Production branch. You can even get more granular and just integrate a specific set of changes. It's all up to you.

Annoying

The same feature that makes Perforce so amazing also makes it very annoying. In a word, INTEGRATION. Once you start integrating changes between branches, you will quickly be tempted to do more complex integrations. Well... my advice to you is just say NO. Keep things as simple as possible. The reason? Odds are that you will encounter a situation where you need to roll back one or more files to a previous version. If you keep your changes as simple and specific as possible, then a rollback is no problem. Just integrate to the version prior to the one where you made your changes. However, if you do a lot of changes and then need to roll back, Perforce will force you to merge you previous changes by hand. Take the word of someone who's done this. It's not fun.

Summary

Perforce is truly a coder's version control system. Just about anything you throw at, it can handle it, either out of the box or through the enormous number of third-party plugins, scripts and triggers. It's well worth the time to learn, and best of all... It's Free!

My boss asked me this question today. I'm going to twist it around a bit and tell you what I've wanted out of life.

Over the years, I've had several different answers: 1) 1992 - I want to work outside, where I can get fresh air and exercise.

I worked on water pipelines in Griffith Park, for the City of Los Angeles

2) 1995 - I want to be the hottest DJ on Los Angeles

Part-time job DJ'ing in several Hollywood nightclubs.

3) 2000 - I want to build the next hot app. for a dot com startup, and become a millionaire.

I built the app. It became hot and got sold. I didn't become a millionaire.

4) 2002 - I want a job.

Lead developer for an entertainment company.

5) 2004 - I want to build something significant.

Development manager for a pharmaceutical company.

6) Today - I want to enjoy life

Team lead for a large professional services company.

I have found that the bigger picture has become much more important to me lately.

Sure, I have the usual problems and frustrations at work. But I don't take them personally anymore. I would rather focus my attention on more enjoyable things, like where I'm going this weekend, or anticipating the delivery of a box of my favorite cigars.