So long, Kodak

I found out yesterday that Kodak has shut down the Digital Cinema group that I belonged to for over 6 years, a victim of a Kodak’s inability to keep up with an incredibly rapidly changing marketplace. Some years before that, I’d had the pleasure to work with many of the same people on a product called “Cineon”, a very high end post production and digital editing program for movies. Alas, technology marched on faster than we did and today people are doing on their Macintoshes and PCs what we were doing on 16 processor million dollar SGI Onyx computers.

But in both cases, I was working with the finest group of programmers, QA people, applications specialists and sysadmins it’s ever been my pleasure to work with (with the possible exception of GeoVision, which was also exceptional). And although I might be cutting my own throat because I’m still in the job market and many of them will be entering the job market very shortly, I sent out this message to the Peernet Rochester Yahoo Group.

I just found out that my old colleagues on the Digital Cinema team at Kodak all got their notices today. And while I’m probably going to be competing with them for some of the same jobs, I’d just like to put a shout out to any hiring managers here to let them know that if you see a software developer or tester with experience in the Kodak Theatre Management System on their resume, you could not do better than to hire them. They are positively the best group of people I’ve worked with in my 25 years of working all over the world.

Ok, if there was some way to put these things on a scale and see how it balances, I’d probably put the team at GeoVision (not the Albany group, the original ones) and the Cineon team as tied for first best, and the Digital Cinema group as a fairly close second, and a couple of the people at SunGard right up there.

Man, I hope we all end up employed again soon. And I hope we all end up working together some time.

Oh, and if you’re one of my former colleagues from Kodak, give me a shout off-line and I’ll hook you up with the Peernet group – it’s really been helpful.

So… C++? Delphi? Markov Chains?

I have a line on a job that involves porting some code that was originally written in R, then in Delphi, and now the researcher wants it re-written in C++, turned into multi-processor/multi-computer friendly (using MPI?), and turned into a plug-in for R. The program as it is now is pretty primitive – he apparently just puts a bunch of parameters into the actual Delphi code then recompiles and runs, and it outputs into a data file. Obviously the first step would be to have a wrapper program that gets the parameters from a data file, and later a wrapper that gets the parameters from however R passes them to plugins.

It’s been a while since I used C++, and the language has changed a lot since then. Name spaces, STL, Boost, auto_ptr, all this stuff is new to me. It’s going to take some frantic reading to get up to speed. Even worse, I have to read the existing code, which means learning a bit of Delphi/Pascal. And I’m going to have to find a decent IDE for C++ – although the consensus on StackOverflow seems to be to go back to the way I’ve always worked until I started using Eclipse last year: gvim, make, gdb, and a web browser open to the man pages.

Even better, the job would mean working from home. The dogs will be happy about that.

First sign of the end times

I knew the Digital Cinema project that I’d been on for 6 years was doomed. But I didn’t know how doomed until the last week or so, when former colleagues on that project have suddenly started responding to the LinkedIn invitations to connect that I sent them a year ago. I’m guessing there is a lot of resume polishing and network building going on there right now. I’d say “Poor bastards”, but I’m in no better shape right now, except I did all that 6 months ago.

Got a Google Wave account

First impressions on Google Wave:

  1. Who thought that bringing back OpenLook’s “elevator” scroll bars was a good idea? Every user interface expert in the world said they were a bad idea then, and they’re still a bad idea. Actually these aren’t exactly like OpenLook’s scroll bars – instead they move some times, and sometimes they don’t, and they’re just weird.
  2. Why does Google Gears say it’s installed on my browser, but the actual Gears functionality (like being able to drag and drop pictures on Wave) not work? I tried some of the demo programs on the Gears web site and they don’t work either. Is there something I’m missing?

I wish there were more of us on Wave. It looks like a great tool for building project docs in a way that’s less likely to turn stale than just putting up a wiki and saying “update it everybody”.