News for hackers. Stuff that matters.
Re:How To Identify A Lame Programming Job by joshu on Thursday December 03, 2009 @06:03PM (#975429)
I like the "what source control" question from the comments. They should use one and it shouldn't be sourcesafe.

Many of these are pretty reasonable. Dunno that travel is that bad a problem...

Re:How To Identify A Lame Programming Job by gaius on Friday December 04, 2009 @08:51AM (#976315)
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.

Re:How To Identify A Lame Programming Job by gaius on Friday December 04, 2009 @08:52AM (#976320)
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.

Re:How To Identify A Lame Programming Job by joshu on Sunday December 06, 2009 @11:35PM (#980712)
Yeah, I guess so.

At one point I lived in NYC and worked in London. And loved it. Hell of a commute, though.