By mswatcher
via aaronsw.com
Published: Nov 30 2009 / 13:07
There are three questions you have when you’re hiring a programmer (or anyone, for that matter): Are they smart? Can they get stuff done? Can you work with them? Someone who’s smart but doesn’t get stuff done should be your friend, not your employee.
-
Send me a patch for that
-
Why (and How) to Replace Amazon SQS with MongoDB
-
Where Tcl and Tk Went Wrong
-
How POW saved my Ruby on Rails Education
-
Wyse CEO to Discuss Leading Trends in Mobility and Cloud Computing at the Stifel Nicolaus Technology & Telecom Conference 2012
-
Background audio in Windows Phone 7.5
Comments
cherouvim replied ago:
well said!
serps replied ago:
Reminds me of this article: http://www.joelonsoftware.com/articles/GuerrillaInterviewing3.html , especially this bit:
"[...] how do you know whether to hire someone?
In principle, it’s simple. You’re looking for people who are
1. Smart, and
2. Get things done.
That’s it. That’s all you’re looking for."
Miloskov replied ago:
Wonderful!!. The hiring people should really read this method, I think is the best.
bhargett replied ago:
Sounds good and all that, but it seems this interview process will take about 6 hours or more. How is this going to work for someone who is looking to move? This only works for the unemployed it seems.
Obdurodon replied ago:
Joel Spolsky called . . . from 2007. He wants his "smart and gets things done" schtick back.
trelliot replied ago:
"Smart" - a relative term
"get things done" - in what time frame
"can you work with them" from your abrupt post, probably not
Voters For This Link (58)
Voters Against This Link (5)