Nicky McCurdy nickserv

gem install pry

require 'pry'

# Fix Dropbox
fs.inotify.max_user_watches = 100000

Unit 2

{
  "a" => 1,
  "b" => 2,
  "c" => 3,
  "d" => [1, 2, 3]
}

Write great commit messages. Your commit messages should start with a short description on one line, capitalized and in the present tense.
Like your software, your commits should be cohesive. Try to keep the contents of a commit related, unless you need to generate/edit a lot of files for a good, specific reason. If you suddenly realize that you want to commit something unrelated to your original uncommited changes, you should probably use git stash to save away unrelated changes before you commit.
Commit early. Commit often. If you wait too long to commit, the scope of your commits may be harder for others to understand, and you will run into merge conflicts more frequently.
Be careful with --patch. It can be very useful, though it also makes it easier to commit portions of your changes that you haven't tested without the rest of your changes.
__Avoid committing binary fi

	#!/bin/bash
	# Updates Bower packages and reinstalls latest versions of Bootswatch themes

	function bootswatch {
	pushd components/bootstrap.css/css > /dev/null
	for theme in $*; do
	echo "Downloading $theme theme"
	curl http://bootswatch.com/$theme/bootstrap.css -so bootstrap-$theme.css
	curl http://bootswatch.com/$theme/bootstrap.min.css -so bootstrap-$theme.min.css
	done

	// see http://blog.jquery.com/2011/11/03/jquery-1-7-released/

	$('a').bind('click', myHandler);
	$('a').on('click', myHandler);

	$('form').bind('submit', { val: 42 }, fn);
	$('form').on('submit', { val: 42 }, fn);

	$(window).unbind('scroll.myPlugin');
	$(window).off('scroll.myPlugin');

	require 'octokit'
	require 'colorize'

	def create_logged_in_client
	puts 'Logging into GitHub. Don\'t worry, I won\'t save your credentials.'
	print 'GitHub username: '
	username = $stdin.gets.strip
	print 'GitHub password: '
	password = begin
	`stty -echo` rescue nil