As an interviewer, I always ask about version control. Doesn't matter which one the candidate has used, but if they can't talk fluently about it, that's a red flag. It's a proxy question for what I really care about, which is, has worked on a large complex system in collaboration with others.
Re:How To Identify A Lame Programming Job
by pwnstigator on Thursday December 03, 2009 @08:43PM
(#975622)
Why would a developer be traveling frequently?
Also, business travel sucks, especially if you're entry-level.
If your product is a "platform" then you may often be visiting customers to work directly with their developers.
I agree on the travel. It can sound exciting from the outside, but airports, taxis, hotels and meeting rooms look the same whatever city or country you're in. Eating room service 5 nights a week gets old real quick.
Many of these are pretty reasonable. Dunno that travel is that bad a problem...