Archive for February, 2008

Effective Concurrency … so far

Friday, February 22nd, 2008

Following on from a previous post about The Pillars of Concurrency, here are links to the full set of Herb Sutters “Effective Concurrency” column topics (as of Feb 2008) …

The Pillars of Concurrency
How Much Scalability Do You Have or Need?
Use Critical Sections (Preferably Locks) to Eliminate Races
Apply Critical Sections Consistently Avoid Calling Unknown Code While Inside a Critical Section
Use Lock Hierarchies to Avoid Deadlock
Break Amdahl’s Law!
Going Superlinear

These are an excellent set of articles on the subject of concurrency and programming for multi-core that analyzes the many facets of the subject – from background theory, to locking and on to achieving scalability and performance.

Hiring Good Programmers

Saturday, February 16th, 2008

The company that I work for is currently embarking on a hiring spree. So I thought it would be a good idea to refresh my interviewing skills before I launch myself into the hiring process.

A recent Coding Horror entry highlights “The Years of experience myth” which is the inadequacy of trying to “match– exactly and to the letter– some highly specific laundry list of skills”. Unfortunately when dealing with some recruitment agencies, I find this an all too common practice. Instead it is vital to remember that “… what software developers do best is learn. Employers should be loooking for passionate, driven, flexible self-educators who have a proven ability to code in whatever language — and serving them up interesting projects they can engage with.”

Joel Spolsky sums up the characteristics that employers should be looking for in future employees as “Smart and Gets Things Done“.

So, now that we’ve figured out what to look for in a candidate, lets look at some resources that give tips for screening CVs, conducting phone screens or face to face interviews.

And finally since the phone screen is probably the most important stage, it’s worth highlighting the two common critical mistakes that an interviewer could make in the phone screen:

  1. Don’t let the candidate drive the interview. The interviewer should do most of the talking, guiding the conversation along until they’re satisfied the candidate knows the answers to the questions (or has given up).
  2. Watch out for one-trick ponies. Candidates who only know one particular language or programming environment, and protest complete ignorance of everything else, are a giant red warning flag.