clemens

# inspired by http://ariejan.net/2010/08/23/resque-how-to-requeue-failed-jobs

# retry all failed Resque jobs except the ones that have already been retried
# This is, for instance, useful if you have already retried some jobs via the web interface.
Resque::Failure.count.times do |i|
  Resque::Failure.requeue(i) unless Resque::Failure.all(i, 1)['retried_at'].present?
end

# retry all :)
Resque::Failure.count.times do |i|

hpneo

GMaps = function(options){
  this.div = $(options.div)[0];
  this.markers = [];
  this.polygon = null;
  this.infoWindow = null;
  this.map = new google.maps.Map(this.div, {
    zoom: 15,
    center: new google.maps.LatLng(options.lat, options.lng),
    mapTypeId: google.maps.MapTypeId.ROADMAP
  });

1st8

description   "God Process Monitoring"
author        "Christoph Geschwind <christoph@mixxt.net>"

start on runlevel [2345]
stop on runlevel [!2345]

respawn              # respawn the service if it dies
respawn limit 5 10   # stop respawning if it fails 5 times in 10 seconds

pre-start script

lovasoa

WARNING : This code now lives in its own github repository: lovasoa/fast_array_intersect. It is also published on npm: fast_array_intersect

Array intersect

Fastest function to intersect a large number of big arrays in javascript, without dependencies

• The compressed version is only 345 caracters long.
• Faster than common libraries, even a large number of arrays, or on very big arrays. (See benchmarks)

sbeam

#!/bin/bash
### BEGIN INIT INFO
# Provides:          thin
# Required-Start:    $local_fs $remote_fs
# Required-Stop:     $local_fs $remote_fs
# Default-Start:     2 3 4 5
# Default-Stop:      S 0 1 6
# Short-Description: thin initscript
# Description:       thin
### END INIT INFO

fukata

PATH=/home/git/.rbenv/bin:/home/git/.rbenv/shims:/var/www/gitorious/script:/opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/local/sbin:/bin:/sbin:/usr/bin

dinnouti

<%= f.input :nome, :collection => get_schools_name, :include_blank => false, :input_html => {:rel => 'autocomplete', :data_default => @school.nome} %>

mikluko

set daemon 30 with start delay 60
set logfile syslog facility log_daemon
set httpd port 2812
    allow localhost

set mailserver localhost
set alert alert@example.com but not on { instance }

mail-format {
    From: noreply@example.com

jakeonrails

data:text/html, <style type="text/css">#e{position:absolute;top:0;right:0;bottom:0;left:0;}</style><div id="e"></div><script src="http://d1n0x3qji82z53.cloudfront.net/src-min-noconflict/ace.js" type="text/javascript" charset="utf-8"></script><script>var e=ace.edit("e");e.setTheme("ace/theme/monokai");e.getSession().setMode("ace/mode/ruby");</script>

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.