mariusGundersen

#!/usr/bin/env bash
# MIT © Sindre Sorhus - sindresorhus.com

# git hook to run a command after `git pull` or `git checkout` if a specified file was changed
# Run `chmod +x post-checkout` to make it executable then put it into `.git/hooks/`.

changed_files="$(git diff-tree -r --name-only --no-commit-id HEAD@{1} HEAD)"

check_run() {
	echo "$changed_files" | grep --quiet "$1" && echo " * changes detected in $1" && echo " * running $2" && eval "$2"

lsiden

#https://gist.github.com/tlowrimore/5162327
#http://stackoverflow.com/a/15413611/270511

module ActiveRecord::UnionScope
  def self.included(base)
    base.send :extend, ClassMethods
  end
  
  module ClassMethods
    def union_scope(*scopes)

sebastianseilund

/**
 * `Ember.MergedArray` is an array that observes multiple other arrays (called source arrays) for changes and includes
 * all items from all source arrays in an efficient way.
 * 
 * Usage:
 * 
 * ```javascript
 * var obj = Ember.Object.create({
 *   people: [
 *      {

maccman

$ = jQuery

queues  = {}
running = false

queue = (name) ->
  name = 'default' if name is true
  queues[name] or= []

next = (name) ->

alexbartlow

class Message < ActiveRecord::Base
  scope :last_two_weeks, -> {
    where(:created_at => (2.weeks.ago..Time.now)) 
  }
  
  scope :for_month, (date) -> {
    where(:created_at => (date.beginning_of_month..date.end_of_month))
  }
  
  def self.sum_word_count

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

abscondment

Okay, Kids, Here We Go...

"What You Need To Know About Your Next Domain Name"

I highly respect what Fred has done, and continues to do, to help entrepreneurs and for that I'd like to "give back" myself... and I'm posting anonymously as I have nothing to gain in anyway by sharing this information...

I'm a serial Internet entrepreneur since 1990 (pre-Web). I've been involved in hundreds of projects online (have built more than one Top 500 web site) and I've been a very active and successful domain name 'trader' along the way.

I've personally owned over 50,000 domains on and off during the past 15+ years. I've been involved in some million$+ deals, and have owned some domains that you know of (but I won't name). I've also been involved in 1,000s of smaller deals. So this is a topic I know very well.

mislav

Jim Weirich:

This is how I explain it… Ruby has Procs and Lambdas. Procs are created with Proc.new { }, lambdas are created with lambda {} and ->() {}.

In Ruby 1.8, proc {} creates lambda, and Ruby 1.9 it creates procs (don't ask).

Lambdas use method semantics when handling parameters, procs use assignment semantics when handling parameters.

This means lambdas, like methods, will raise an ArgumentError when called with fewer arguments than they were defined with. Procs will simply assign nil to variables for arguments that were not passed in.

piscisaureus

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = git@github.com:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:

jlong

var parser = document.createElement('a');
parser.href = "http://example.com:3000/pathname/?search=test#hash";

parser.protocol; // => "http:"
parser.hostname; // => "example.com"
parser.port;     // => "3000"
parser.pathname; // => "/pathname/"
parser.search;   // => "?search=test"
parser.hash;     // => "#hash"
parser.host;     // => "example.com:3000"