Episode 56: Recent experiences with Adobe AIR and the job market
No, those aren't related, but I've got a couple small rants about Adobe's Flex/AIR video system, why I moved back to Windows Media, and (separately) a small but insightful(!) take on the current state of job boards and how job seekers and employers find each other (hint - it stinks right now).
- Google Chrome
- Google's Chrome Browser
- WebDevJobs
- Post job openings for web development positions
- Adobe AIR DevNet
- Developer area for Adobe AIR
- Windows Media Services
- Windows Media Services info page
- Boulder Job Fair
- Win a free trip to Boulder!
Comments



Logan says on Sep 30, 2008 @ 06:50 PM:
What would we do without twitter?
Downloaded and listening to it now.
Michael Kimsal says on Sep 30, 2008 @ 10:09 PM:
We'd probably all get a lot more 'work' done. :)
Rob Christensen says on Oct 1, 2008 @ 05:12 AM:
Hi Michael,
Wow, excellent podcast and thank you for sharing some of your frustrations around the application you were trying to build. I'd be interested in following up with you on this topic. Please feel free to send me an email.
Thanks,
-Rob Christensen
Product Manager, Adobe AIR
Shawn Hartsock says on Oct 2, 2008 @ 05:23 PM:
Ah... the job market. Employers can't find qualified talent and job seekers can't find qualified employers. What to do?
A professional association? A guild? Open source contribution as a prereq? A code dojo?
Michael Kimsal says on Oct 4, 2008 @ 03:36 PM:
Hoisted by my own petard. I had a long reply to this and then lost it due to the 'preview' mode, guarding against spam. :(
Reduced reply - not sure that guilds or associations will help much. They exist already to some degree, but I'm not sure they've helped people get jobs or find workers. I recently became 'zend certified' (last month) but I was able to get PHP work well before that - certification had not been an issue for places I'd worked.
Reputation helps some, but not everyone can have world-known reputations. It's just not feasible for 100,000 developers to be known world-wide (or even regionally) by name and reputation - people can't process that much information!
That said, word of mouth has been the biggest single factor in my working life, working both ways (people referring work to me and me referring work to other people). Places like linkedin.com help the 'word of mouth' network further as well.
Kaity G. B. says on Oct 4, 2008 @ 03:50 PM:
Why not use ffmpeg?
I agree that Adobe tries to own flash but the easiest way to have resolved this would have been to use ffmpeg's video recording option. One simply command can record from 1 or more video & audio sources & than stream or record the output in literally any format, quality, & etc that you would like. I'd write some examples but ffmpeg's man page, wiki, & etc documentation covers it very well. I've used it to stream meeting, wedding, & presentations. It really is flexible & should feel this gap & def be platform independent.
I can't believe after all of your show's I'm just now learning that you're a windows developer, hmm. I would have guessed you where a Linux programmer. Of course that does fill in some blanks.
Michael Kimsal says on Oct 4, 2008 @ 08:53 PM:
What blanks does it fill in? :)
I'm not a Windows developer. Likely true hard core Windows developers would laugh at my seemingly idiotic attempts to do something so 'basic' as to encode video.
You're the second person to suggest ffmpeg, so this is obviously something I'll have to dig in to further. I wasn't aware that ffmpeg would allow for all this sort of stuff (embedding in to UI, etc.). However, at first blush, it does look like it's GPL (LGPL, but other parts are GPL) and I'm not 100% certain what effect that would have on the redistributability of this app.
My background:
Started with BASIC on ZX81 in 1981. Moved to C128 BASIC and machine code (lovely 6502 with JMPs everywhere!). Migrated in to PC era with a brief diversion in to Amiga. Did VB3-5 development, then Notes, then started doing web stuff in Perl in late 1995, then PHP2 (PHP/FI) in early 1996. Did some ASP in late 90s (who didn't?!) then back to primarily PHP, with dollops of Perl, Python, Java, CF and other stuff over the years. This latest project happens to be .NET based, but coming back to the Windows world reminds me of all the things I have *not* missed about developing in MS (although there's certainly some nice things too).
So, in short, I'm not particularly a 'windows' developer - I'm a generalist developer (I think) but every project has to be done in *something*. In this particular case, Windows was the most practical to meet the client's needs as they were understood at that time, along with budgetary and time constraints (time being the biggest one). I have XP, Ubuntu and OSX running at the house, but I spend most of my time in Ubuntu.
Peter McDonald says on Nov 1, 2008 @ 03:30 PM:
Finally got around to listening to this episode and listened to your comments on chrome with interest.
Of course the security holes would not necessary have been in the limelight at the time but of course as it was beta security holes were expected.
However it has been a month so far and I have never came across an announcement that a new version has been released. I downloaded the exe again and reinstalled it and found the security holes have been repaired.
Why have Google never announced this and just as disturbing the version number from prior to the upgrade is the same as it was after the new install. Why are they keeping version numbers the same? And how many people are actually still using those original susceptible versions?
Michael Kimsal says on Nov 9, 2008 @ 04:20 AM:
Hello Peter:
Good point, if it's true. I've no reason to doubt you, but don't know much about that particular issue. I'll see if I can dig anything up on it. Slightly disturbing, to say the least. Google's mostly done 'in the cloud' stuff and can roll out new versions whenever with fixes/etc and no one necessarily notices. But to do that same thing with desktop software without even updating version numbers is not a good practice to adopt.