Mike Coyle’s Weblog

Joel Spolsky has a great article on The Phone Screen, prompting me to jot down my $.02 on the topic.

In a prior life, I used to do tons of technical phone screens for everything from C# developers to Linux sysadmins. There is one concept that drives my interviewing style: You never have to ask a Navy SEAL if they can swim.

Here’s why: There are many skills, experiences, etc. that intrinsically require mastery (or at least competency) in smaller supporting skills. I’ve found that if I can validate these higher-level skills, I can reasonably assert that the candidate is competent in a cascade of supporting topics. It also allows you to sidestep the Buzzword Bingo that so many candidates feel that they need to play.

I like to ask questions that intrinsically flush out other areas of expertise (or lack thereof) in the process of being answered. For example, I never ask someone if they are proficient in [INSERT TOPIC HERE].

Rather, I ask them what they like or dislike about it, and why. If they have an opinion regarding likes and dislikes, it’s usually grounded in an understanding of the topic at hand, plus some basis for making the comparison. Plus, I’ve found that canned answers regarding opinions are easier to sniff out, because there’s no heart behind them.

The folks that eat and breathe technology have lukewarm opinions either way on very few topics.

I also ask a lot of questions about failures, bad designs, etc. I’ve found that for every big project, there are a bunch of junior folks who wait two years and then profess to be the project lead. The imposters always remember the cool stuff and the brag-worthy statistics (”we saved the customer $30M…”). However, only the genuine project leads can speak convincingly about the all-night debugging session in the office with the CIO the day before the big demo, the nasty integration details, hard-to-reproduce library conflicts, etc.

Also, here’s one more tip: I’ve found that if a candidate ever answers a question with word “Polymorphism”, they are always trying to bluff their way through the interview using big words. I know this because I never ask questions where the word “Polymorphism” by itself is a reasonable answer.

John Hagel has an interesting take on a Forbes article by Rich Karlgaard about Zero-Sum thinking, particularly as it relates to the business community’s unfortunate embrace of this often-flawed world view.

I had never considered zero-sum thinking as a “sickness” as Mr. Karlgaard suggests, but I think that this analogy is spot-on.

My personal rule of thumb for noticing that your falling into the Zero-Sum trap? When your inner Daffy Duck chimes in during planning or negotiations with:
“It’s mine, you understand? Mine, all mine! Get back in there! Down, down, down! Go, go, go! Mine, mine, mine!”, then you may be missing an opportunity to, as economists are apt to say, grow the pie.

Paul Graham has posted his somewhat famous How To Make Wealth essay online. This is my favorite chapter from his book Hackers & Painters. To me, it’s the most succinct depiction that I’ve seen of the “laws of physics” that influence business, not to mention its relevance to software developers.

As the saying goes, “You cannot always get rid of your troubles, but you can trade the problems that you have for the problems that you want”. I believe that “How to Make Wealth” does a pretty good job of illustrating what trades have the highest long-term return.

Web 2.0. As is always the case with Paul’s essays, it’s a good read.

My favorite passage:

Google doesn’t try to force things to happen their way. They try to figure out what’s going to happen, and arrange to be standing there when it does. That’s the way to approach technology– and as business includes an ever larger technological component, the right way to do business.

For those of you following along at home, this Judo-esque display of market timing and technical acumen is Reason #693 for why Google rocks.