[LRUG] Code samples: To do or not to do

[Luis Correa d'Almeida]

Vahagn -

On Tue, Apr 7, 2009 at 12:41 AM, Vahagn Hayrapetyan <vahagnh at gmail.com> wrote:
> Matthew:
>
> Absolutely, I agree that one of the best ways a programmer can demonstrate
> his ability is to have open-source contributions. Having working, cool /
> alternative webapps online is another option (which I have personally
> favoured so far).
>

+1 Contributing to open source is major. Shows that you care about
your craft enough to spend your personal time on open source. It also
shows that you care about freedom in software and the community beyond
your immediate circle. Also tends to show initiative and drive, which
for an employer is important, specially in high performing teams.

> To set things straight, I should perhaps have noted that my post mainly is
> about the situation where our theoretical programmer has not yet contributed
> with any public code - either because he has chosen to prioritize otherwise
> or because he is still new to a language / ecosystem (Ruby obviously in
> question here).
>

Our interviewing process involves a technical exercise, were the
candidate is asked to solve a problem using the language we are
*primarily* hiring for. If we believe that what the candidate has
demonstrated is in line with what we are looking for, then the
candidate will pair with one of our developers for about 1h30 on
extending the solution to that original problem.

I have never asked for code excerpts. We are much more interested in
the candidate's analytical and problem solving skills.

> Cheers,
> Vahagn

Best,

Luis

>
> On Tue, Apr 7, 2009 at 1:34 AM, Matthew Rudy Jacobs
> <matthewrudyjacobs at gmail.com> wrote:
>>
>> 2009/4/7 Vahagn Hayrapetyan <vahagnh at gmail.com>:
>> > 1) Is it common for programmers / developers in the UK to attach code
>> > samples with their CVs in order to heighten their chances of
>> > recruitment?
>> > 2) Should it be the norm for programmers / developers (regardless of
>> > geography) to attach code samples with their CVs in order to heighten
>> > their
>> > chances of recruitment?
>>
>> Ultimately, any employer is going to want to see some code before they
>> employ you
>> (or at least talk to you about it)
>> I can't see how you'd avoid that.
>>
>> I'm lucky in that I have a million projects on my github.
>> So I always point people straight there.
>>
>> I remember a couple of years ago, it was really frustrating.
>> I hadn't had the time to contribute to OpenSource projects, github
>> didn't exist....
>> and I had to make up code to send people.
>> It was really annoying.
>>
>> But,
>> I can't believe ALL the Recruiters you've spoken to have asked for code.
>> Most of them have no idea what good code looks like.
>>
>> I'd say the process should be;
>>
>> 1. send a CV (link to blogs / github if you have them)
>> 2. do a phone / informal pub meetup
>> 3. do a proper face to face interview
>> 4. take a look at some code, or discuss coding practice.
>>
>> :s
>>
>> But yeah.
>> Everyone should have code on the internet somewhere.
>> Unfortunately some people do have lives, though.
>> So maybe "MUST HAVE A GITHUB PROFILE" is an unfair requirement right now.
>> _______________________________________________
>> Chat mailing list
>> Chat at lists.lrug.org
>> http://lists.lrug.org/listinfo.cgi/chat-lrug.org
>
>
> _______________________________________________
> Chat mailing list
> Chat at lists.lrug.org
> http://lists.lrug.org/listinfo.cgi/chat-lrug.org
>
>