Skip to content

Instantly share code, notes, and snippets.

View ryannealmes's full-sized avatar

Ryan-Neal Mes ryannealmes

View GitHub Profile
credit to https://github.com/mdkrog
git checkout development
git pull origin development
git checkout your-local-branch
git rebase -i development
git push -f origin your-local-branch
git checkout development
git merge your-local-branch --ff-only
git push origin development
credit to https://github.com/mdkrog
git checkout development
git pull origin development
git checkout you-local-branch
git rebase -i development
git push -f origin your-local-branch
git checkout development
git merge your-local-branch --ff-only
git push origin development

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.

#!/bin/bash
# Exists to fully update the git repo that you are sitting in...
git pull && git submodule init && git submodule update && git submodule status
=Navigating=
visit('/projects')
visit(post_comments_path(post))
=Clicking links and buttons=
click_link('id-of-link')
click_link('Link Text')
click_button('Save')
click('Link Text') # Click either a link or a button
click('Button Value')