Andy Waite andyw8

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 = [email protected]: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:

Benchmark Bundler

Because loading gems can take longer than you think

$ curl -fsSL https://gist.github.com/jherdman/5025684/raw/a3ccd4b5308723245706b4ae315845fe951b4473/benchmark.rb | ruby
............................................................[DONE]

Gem                            Time(sec)     Pct %
--------------------------------------------------

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.

The quick fix

Assuming you have homebrew installed and you use bundler, you can fix this issue by doing the following:

gem uninstall nokogiri libxml-ruby
brew update
brew uninstall libxml2
brew uninstall libxslt
brew install libxml2 --with-xml2-config

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.

	require 'spork'

	Spork.prefork do
	require 'rspec'
	require 'pry'

	# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
	RSpec.configure do \|config\|
	config.treat_symbols_as_metadata_keys_with_true_values = true
	config.run_all_when_everything_filtered = true

	#!/usr/bin/env ruby

	if name = ARGV.first
	path = `gem which #{name}`
	readme = Dir.glob(File.join(File.dirname(path), "../", "README.{md,markdown}")).first
	fail "Failed to find readme for gem '#{name}'" unless File.exist?(readme)
	puts File.read(readme)
	else
	puts "Usage: gem-man gem_name"
	end

	require 'childprocess'

	guard 'shell' do
	watch %r{^app/(.+)\.rb$} do \|m\|
	`killall rake`

	# Why this:
	# - spawn a child process to avoid locking Guard
	# - make sure that the child process has stdout and stdin otherwise it crashes
	# - bonus point: get REPL access in the simulator!

	class NSObject
	def method_missing(meth, *args)
	obj_c_meth = meth.split('_').inject([]){ \|buffer,e\| buffer.push(buffer.empty? ? e : e.capitalize) }.join
	if respond_to?(obj_c_meth)
	send obj_c_meth, *args
	else
	raise NoMethodError.new(meth.to_s)
	end
	end
	end