Ashwin M ashwin47

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.

This is a post by Joel Spolsky. The original post is linked at the bottom.

This is such a common question here and elsewhere that I will attempt to write the world's most canonical answer to this question. Hopefully in the future when someone on answers.onstartups asks how to split up the ownership of their new company, you can simply point to this answer.

The most important principle: Fairness, and the perception of fairness, is much more valuable than owning a large stake. Almost everything that can go wrong in a startup will go wrong, and one of the biggest things that can go wrong is huge, angry, shouting matches between the founders as to who worked harder, who owns more, whose idea was it anyway, etc. That is why I would always rather split a new company 50-50 with a friend than insist on owning 60% because "it was my idea," or because "I was more experienced" or anything else. Why? Because if I split the company 60-40, the company is going to fail when we argue ourselves to death. And if you ju

	# first we download the list of IP ranges from CloudFlare
	wget https://www.cloudflare.com/ips-v4

	# set the security group ID
	SG_ID="sg-00000000000000"

	# iterate over the IP ranges in the downloaded file
	# and allow access to ports 80 and 443
	while read p
	do

	var child_process = require('child_process');

	// exec: spawns a shell.
	child_process.exec('ls -lah /tmp', function(error, stdout, stderr){
	console.log(stdout);
	});

	// execFile: executes a file with the specified arguments
	child_process.execFile('ls', ['-lah', '/tmp'], function(error, stdout, stderr){
	console.log(stdout);