ryansobol

Originally published in June 2008

When hiring Ruby on Rails programmers, knowing the right questions to ask during an interview was a real challenge for me at first. In 30 minutes or less, it's difficult to get a solid read on a candidate's skill set without looking at code they've previously written. And in the corporate/enterprise world, I often don't have access to their previous work.

To ensure we hired competent ruby developers at my last job, I created a list of 15 ruby questions -- a ruby measuring stick if you will -- to select the cream of the crop that walked through our doors.

What to expect

Candidates will typically give you a range of responses based on their experience and personality. So it's up to you to decide the correctness of their answer.

kiwiupover

$width: 4%;
.inpad {padding:0 $width/2;}
.inpad.four { width: 30.75 - $width !important; }
.inpad.five { width: 39.45 - $width !important; }
.inpad.six { width: 48 - $width !important; }
.inpad.seven { width: 56.75 - $width !important; }

li .inpad {padding:5px 5%;}

.inpad.panell {

gurglet

#!/bin/bash

# Git post checkout hook.
# Reminds you of South migration changes when switching branches.
# Can be useful when you are when you are testing out a branch from
# someone else that requires migrations.
# Put the file in .git/hooks/post-checkout

PREVIOUS_HEAD=$1
NEW_HEAD=$2