dfurber

# These are my notes from the PragProg book on CoffeeScript of things that either 
# aren't in the main CS language reference or I didn't pick them up there. I wrote 
# them down before I forgot, and put it here for others but mainly as a reference for 
# myself.

# assign arguments in constructor to properties of the same name:
class Thingie
    constructor: (@name, @url) ->

# is the same as:

acwright

require 'sinatra'
require 'action_mailer'

class Mailer < ActionMailer::Base
  def contact
    mail(
      :to      => "test@example.com",
      :from    => "test@example.com",
      :subject => "Test") do |format|
        format.text

marcomd

#Session controller provides a token
#/controllers/api/sessions_controller.rb
class Api::SessionsController < Devise::SessionsController
  before_filter :authenticate_user!, :except => [:create]
  before_filter :ensure_params_exist, :except => [:destroy]
  respond_to :json

  def create
    resource = User.find_for_database_authentication(:email => params[:user_login][:email])
    return invalid_login_attempt unless resource

aseemk

bunyan = require 'bunyan'
restify = require 'restify'
requireDir = require 'require-dir'

middleware = requireDir './middleware'
routes = requireDir './routes'
settings = require './settings'

app = restify.createServer
    name: 'Foo Bar API'

kylerush

#!/usr/bin/env python

#install the follow first:

#sudo easy_install pip

#sudo pip install -U boto

#sudo pip install configparser

chrismytton

App.ProgressBar = Ember.View.extend
  classNames: ['progress']
  template: -> '<div class="bar"></div>'
  percent: 0

  percentDidChange: (->
    percent = @get 'percent' || 0
    @$('.bar').css 'width', percent + '%'
  ).observes('percent')

kenkeiter

class User extends Spine.Model

  url: ->
    '/' + @username

  collections: ->
    unless @collection_klass?
      @collection_klass = _.clone(Collection)
      @collection_klass.parent = this
    @collection_klass

ryansobol

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.

adamwiggins

Make it real

Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.

Ship it

Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.

Do it with style

tpitale

#!/bin/bash

BACKUP="/tmp/s3/db"
DATE=`date +"%Y-%m-%d"`
DIR="${BACKUP}/${DATE}/"

if [ ! -d $DIR ];
then
	mkdir -p $DIR
fi