bhattisatish

// Original source http://lusob.com/2012/02/tracking-a-football-match-with-html5-and-javascript/
(function( $ ){

	function format(str) {
		for (var i = 1; i < arguments.length; i++) {
			str = str.replace('%' + (i - 1), arguments[i]);
		}
		return str;
	}

bhattisatish

require 'mechanize'
require 'logger'
require 'date'

## Call:
## $ ruby export.rb <gmail> <password>

# https://www.google.com/history/lookup?hl=en&month=11&day=04&yr=2008&output=rss&num=9999

agent = Mechanize.new do |a|

bhattisatish

# Original Source: http://illuminatedcomputing.com/posts/2011/11/disposable-staging-site-on-heroku/
# We use this Makefile to destroy the staging site
# and re-create it based on production.
# This is useful to keep staging current,
# and it's especially nice so we can rehearse deployments.
# If we nuke staging and then deploy the latest code there,
# we can be more confident that the production deploy
# will run smoothly.

PRODUCTION_APP=example

bhattisatish

#!/usr/bin/env sh

##
# This is script with usefull tips taken from:
#   https://github.com/mathiasbynens/dotfiles/blob/master/.osx
#
# install it:
#   curl -sL https://raw.github.com/gist/2108403/hack.sh | sh
#

bhattisatish

#Deploy and rollback on Heroku in staging and production
task :deploy_staging => ['deploy:set_staging_app', 'deploy:push', 'deploy:restart', 'deploy:tag']
task :deploy_production => ['deploy:set_production_app', 'deploy:push', 'deploy:restart', 'deploy:tag']

namespace :deploy do
  PRODUCTION_APP = 'YOUR_PRODUCTION_APP_NAME_ON_HEROKU'
  STAGING_APP = 'YOUR_STAGING_APP_NAME_ON_HEROKU'

  task :staging_migrations => [:set_staging_app, :push, :off, :migrate, :restart, :on, :tag]
  task :staging_rollback => [:set_staging_app, :off, :push_previous, :restart, :on]

bhattisatish

# List of environments and their heroku git remotes
ENVIRONMENTS = {
  :staging => 'myapp-staging',
  :production => 'myapp-production'
}

namespace :deploy do
  ENVIRONMENTS.keys.each do |env|
    desc "Deploy to #{env}"
    task env do

bhattisatish

class Song
  # Regular expressions
  RE = {
    :featured => /(featuring | ?ft\.? |feat\.? |f\. |w\/){1}/i,
    :remixer => / remix| rmx| edit| bootleg| mix| remake| re-work| rework| extended remix| bootleg remix/i,
    :mashup_split => / \+ | x | vs\.? /i,
    :producer => /^(produced by|prod\.? by |prod\. )/i,
    :cover => / cover/i,
    :split => /([^,&]+)(& ?([^,&]+)|, ?([^,&]+))*/i, # Splits "one, two & three"
    :open => /[\(\[\{]/,

bhattisatish

#!/usr/bin/env ruby

require "redis"

redis = Redis.new
redis.keys("*").each do |key|
  val = case redis.type(key)
        when "string"
          redis.get key
        when "list"

bhattisatish

//// some function
//var foo = function ( data ){ console.log(data); }
//// identical to foo(), except can only be called once every 100ms.
//var limitedFoo = trickle(foo, 100);
////
function trickle( fun , waitLength )
{
   var lastCalledAt = 0,
       context = this;

bhattisatish

# Build around a theme
Ensure that you have a theme around the hackathon. It should be generic enough for people to have freedom on what they want to build, but specific enough for people to focus on. There is nothing like a goal oriented hackathon. The energy that can build up is amazing.

If you are running it as an internal event, then make sure you brainstorm/vote on the theme by getting the whole org involved.

Organize the event for at least 2-3 days.Though I have seen 1 night events, rarely anything comes out of those.
If it's an internal event, avoid conducting it over a weekend, however tempting. 

# Logistics
Take care of the food! Three meals, and maybe couple of snack periods. If you can afford it, try to have a full pantry for snacks.