Glance through a few of the examples, maybe 5 or so, to see what kinds of things Elm is doing, what domains they're in, what the code looks like, what other people think Elm is.
_ \ | |
, __ , # (C) Josh Cheek | |
*,_ = # 2015 | |
def __ ___ , # Inspiration | |
*__, **_ # Is | |
putc ___ # Obviously | |
end, def _ *_, # Yusuke | |
**__ # Endoh | |
_. # | |
map {|_ ;__ # And |
var sinon = require('sinon'), | |
Widget = require('../../widget'); | |
describe('My widget', function () { | |
var sandbox; | |
beforeEach(function () { | |
// Create a sandbox for the test | |
sandbox = sinon.sandbox.create(); | |
}); |
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.
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.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> | |
<html> | |
<head> | |
<link rel="stylesheet" href="http://code.jquery.com/qunit/git/qunit.css" type="text/css" media="screen" /> | |
<!-- when.js Promises implementation --> | |
<script src="https://raw.github.com/cujojs/when/master/when.js"></script> | |
<!-- Unit testing and mocking framework --> | |
<script type="text/javascript" src="http://code.jquery.com/qunit/git/qunit.js"></script> |