We want you.

Okay, that was shameless. I'm sorry. It's also not particularly accurate.

I just got out of a meeting with our recruiter, and I got to wondering about the difference between a recruiter's world view and an engineer's. They have a job requisition to fill, and they look for someone with the precise set of skills required for the job at hand.

In engineering, we'd rather look for a bunch of good coders, and let them move between projects as needed, picking up new skills as they go. At Nuance, I've been on 3 different project teams: a VoiceXML interpreter, a j2ee-based (server-side) tool, and a netbeans-based (client-side) tool. If all I'd ever done was write netbeans modules, I wouldn't have learned enough about server-side programming to work on speech application architecture for V-Builder. If I hadn't worked on the VoiceXML interpreter, I wouldn't have known enough to do a really good job on automatic VoiceXML code generation in V-Builder.

So, if you:

• love to code
• you're good at it
• you think speech recognition sounds kinda cool

...then let me know ... whether or not you've ever written a NetBeans module.

You can reach me at RichUnger (at) netbeans.org