Comments on: On Craft http://techbrew.net/articles/200801/on-craft/ Informative geekery on software and technology Mon, 07 May 2012 17:24:57 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Rob http://techbrew.net/articles/200801/on-craft/comment-page-1/#comment-15016 Rob Tue, 08 Jan 2008 13:44:55 +0000 http://techbrew.net/articles/200801/on-craft/#comment-15016 In many jobs now days, candidates are asked to present a portfolio of work. Granted, my view comes from someone who is not a programmer, but I have been asked to provide work examples. I assume many programmers have personal work (not confidential) that can be presented to the interviewer. If this cannot be done, then I think it's important to ask questions about the craft of coding. "What do you like most about exemplary software engineers - what makes them exemplary? How would you rate yourself? Why? What is the biggest pain point to your coding skills? What is the easiest/hardest part of interpreting requirements?" Have a plan that tried to get to the (1) work examples, (2) work style/ethic, and (3) interpersonal/initiative skills. In many jobs now days, candidates are asked to present a portfolio of work. Granted, my view comes from someone who is not a programmer, but I have been asked to provide work examples. I assume many programmers have personal work (not confidential) that can be presented to the interviewer.

If this cannot be done, then I think it’s important to ask questions about the craft of coding. “What do you like most about exemplary software engineers – what makes them exemplary? How would you rate yourself? Why? What is the biggest pain point to your coding skills? What is the easiest/hardest part of interpreting requirements?”

Have a plan that tried to get to the (1) work examples, (2) work style/ethic, and (3) interpersonal/initiative skills.

]]> By: Brooke Kuhlmann http://techbrew.net/articles/200801/on-craft/comment-page-1/#comment-15012 Brooke Kuhlmann Mon, 07 Jan 2008 19:52:40 +0000 http://techbrew.net/articles/200801/on-craft/#comment-15012 Hmm, I fall into the "idealist" category. Although, I wouldn't say I'm miserable as there are alternatives to taking pride in the work you do whether it be those small opportunities while on the job or elsewhere (as you suggest). As for interviews, they are great for getting a chance to study someone in person, observe body language, ask and answer questions, etc. However, this is just talk. What you need is proof. In this day and age, I think the best way to learn about someone (in addition to interviewing and reading the resume) is by studying what they write technically (i.e. blog) or develop (i.e. open source projects) in public. It is these types of individuals that I find most exceptional because they truly enjoy working in the tech industry. These are the kind of people you want to hire. Hmm, I fall into the “idealist” category. Although, I wouldn’t say I’m miserable as there are alternatives to taking pride in the work you do whether it be those small opportunities while on the job or elsewhere (as you suggest).

As for interviews, they are great for getting a chance to study someone in person, observe body language, ask and answer questions, etc. However, this is just talk. What you need is proof. In this day and age, I think the best way to learn about someone (in addition to interviewing and reading the resume) is by studying what they write technically (i.e. blog) or develop (i.e. open source projects) in public.

It is these types of individuals that I find most exceptional because they truly enjoy working in the tech industry. These are the kind of people you want to hire.

]]>