| { | |
| "ecmaFeatures": { | |
| "globalReturn": true, | |
| "jsx": true, | |
| "modules": true | |
| }, | |
| "env": { | |
| "browser": false, | |
| "es6": true, |
| var gulp = require("gulp"), | |
| gutil = require("gulp-util"), | |
| jshint = require("gulp-jshint"), | |
| concat = require("gulp-concat"), | |
| clean = require("gulp-clean"), | |
| connect = require("gulp-connect"), | |
| sourcemaps = require("gulp-sourcemaps"), | |
| bowerPath = "bower_components/"; | |
| var bowerComponents = [ |
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!
- liblinear-ruby: Ruby interface to LIBLINEAR using SWIG
| [ | |
| { "keys": ["super+b"], "command": "run_single_ruby_test", | |
| "context": [ { "key": "selector", "operator": "equal", | |
| "operand": "source.ruby, source.rspec, text.gherkin.feature" | |
| } ] | |
| }, | |
| { "keys": ["super+shift+b"], "command": "run_all_ruby_test", | |
| "context": [ { "key": "selector", "operator": "equal", | |
| "operand": "source.ruby, source.rspec, text.gherkin.feature" | |
| } ] |
| # room_channel.ex | |
| defmodule Stadium.RoomChannel do | |
| use Phoenix.Channel | |
| def join(socket, "lobby", _) do | |
| reply socket, "joined", "you joined" | |
| {:ok, socket} | |
| end |
| # ember-cli | |
| # chat router | |
| `import Ember from 'ember'` | |
| ChatRoute = Ember.Route.extend | |
| setupController: (controller, model)-> | |
| @_super(controller, model) |
-
Data Down / Actions Up
- http://emberjs.jsbin.com/nayaho/edit?html,js - Interdependent select boxes. No observers.
- http://ember-twiddle.com/2d7246875098d0dbb4a4 - One Way Input
-
Plain JSBin's
-
Ember Version Base JSBin's
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.