Osazeme Usen osazemeu

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.

Update and upgrade the system

sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade && sudo apt-get autoremove
sudo reboot

Configure timezone

CHEAT SHEETS

$ command line ruby cheat sheets

INSTALL

$ gem install rspec

UPDATE a fork of this gist has been used as a starting point for a community-maintained "awesome" list: machine-learning-with-ruby Please look here for the most up-to-date info!

Resources for Machine Learning in Ruby

Gems

liblinear-ruby: Ruby interface to LIBLINEAR using SWIG

	=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')

	Hi David,
	I came across your profile online and wanted to reach out about Development
	Opportunities here at Groupon. The company is growing, and we're always
	looking for folks with solid skills that can make positive contribution to
	our continued success. Any chance you'd be open to a quick conversation
	about opportunities, or for any possible networking potential? If so, let me
	know when you're free and we can set up a time to chat. Also, if you are
	interested, it would be great if you could forward a current resume over
	that I can take a look at. I look forward to hearing back from you! Please
	let me know if you have any questions.

	#!/usr/bin/ruby
	require 'rss'

	# Usage
	# $ ./railscasts.rb http://railscasts.com/subscriptions/YOURRAILSCASTRSS/\/
	# episodes.rss
	# OR
	# $ ./railscasts.rb

	p 'Downloading rss index'

	# This is a skeleton for testing models including examples of validations, callbacks,
	# scopes, instance & class methods, associations, and more.
	# Pick and choose what you want, as all models don't NEED to be tested at this depth.
	#
	# I'm always eager to hear new tips & suggestions as I'm still new to testing,
	# so if you have any, please share!
	#
	# @kyletcarlson
	#
	# This skeleton also assumes you're using the following gems:

	# Thee will be more information here when I share the entire problem space I'm working on, but
	# in short, this is preview material for my second talk in a series called "What Computer Scientists Know".
	# The first talk is on recursion, and goes through several examples., leading up to a problem based
	# on a simple puzzle that initial estimates based on performance of a previous puzzle would take years
	# to solve on modern computers with the techniques shown in Ruby. That sets the stage for improving the
	# performance of that problem with threading, concurrency, and related tuning.
	#
	# The second talk is on threading and concurrency, touching on algorithmic performance as well.
	# Using some knowledge of the problem (board symmetry, illegal moves, etc), we reduce the problem space
	# to about .5% of what we initially thought it was. Still, the initial single threaded solution took more

	require 'rails_helper'

	RSpec.describe TodosController, :type => :controller do

	describe "GET #index" do
	#describe "POST #create" do
	#describe "GET #show" do
	#describe "PATCH #update" do (or PUT #update)
	#describe "DELETE #destroy" do
	#describe "GET #new" do