From the Horizon FrontLine

So what's our code name?

I recently asked what's in a name, comparing the original code name of Avalon to the published name of the Windows Presentation Foundation, found in Windows Vista.

As soon as I wrote that, I thought of the new Horizon/SQL fleet management product and said "uh --- what's the codename for that?"

Well, truth be told, there is none. Our DotNet product has a codename of "Athens", I'm not sure if our new accounting system has one but this new version of Horizon is definitely missing a codename. Never had one, and it likely won't get one.

Is that important? Well, I suppose it depends on how much you like to say Horizon/SQL.

Does that mean it's not a big change for existing Horizon users?

Well , yes and no. Horizon/SQL is definitely going to bring in some new changes that I'm very excited about - things that have been talked about for quite some time and will be getting directly into the product. I'll post more on that later today and also provide a link to some videos of some of the functionality to be found.

Will it change the way you work today? The answer? Only if you want it to. If you want to continue dispatching the way you do today, you'll be able to. But it will include many of the things customers have been saying "it would be cool if we could do this..."

I am a big fan of product codenames but this project doesn't have one. Codenames are sometimes inspirational, othertimes a play on words (Sedna for example is a possible candidate for a 10th planet, which is why the next version of Foxpro is named Sedna).

So maybe that's why the last thing on my mind when starting this project was coming up with an internal "codename" for it. There are so many evolutionary features in it, that Horizon isn't just the product name, it also is the "code name".

Andrew MacNeill - AKSEL Solutions: What's in a Name?

posted by Andrew MacNeill @ 8:19 AM