One of the options was to use a google spreadsheet matrix that had to be manually updated each day. Visually it worked well since you could update the numbers and see a history, but there wasn’t really a way to see who was paired on the given day. Also whenever someone left the team you needed to completely re-work the matrix to account for the change. We discussed the options to improve the experience and I decided to write an application to automate the process.

Pairtrix simplifies the process of managing and viewing team pairings by allowing signed in users to manage companies, employees, teams and pairs. Companies are displayed in a list and signed-in users can request membership to view that company’s information. Users who create a company will also have more administrative functions available to them including approving the membership requests for their companies.

Here are the links to the application, code repository and the tracker project. Please feel free to pass along bugs and feature requests.

Site: http://www.pairtrix.com

Github: https://github.com/jgeiger/pairtrix

Pivotal Tracker: https://www.pivotaltracker.com/projects/608423

I usually set dates in my factories to “1/1/2000″ but from now on it will be “12/31/1999″ so I can catch this issue way sooner.

Also check out https://github.com/jeremyevans/ruby-american_date which will solve the issue quickly. (Note, this seems to break using non-American dates (dd/mm/yyyy)

gist: Swap iTerm2 cursors in vim insert mode when using tmux

Thanks and hope it helps someone else.

set :application, "myappname"
set :bundle_roles, "/www/#{application}/current"

Adding the above lines somewhere in your deploy (change as needed) will allow you to override the default and get the deploy working.

It’s interesting that they don’t list “current_release” as an option you can change but if you look at the code it’s being pulled in just like all the others.

items/show.html.haml

.content
 - if @item.user == current_user
  Hello!
This is the rest of the content.

show.html_spec.rb

require 'spec_helper'

describe "items/show" do
  before do
    @user = mock_model(User)
    view.stub(:current_user).and_return(@user)
  end

  context "when logged in as the item owner" do
    it "should display 'Hello!'" do
      assign(:item, stub_model(Item, user: @user))
      render
      rendered.should have_content("Hello!")
    end
  end

  context "when logged in as anyone else" do
    it "should not display the 'Hello!' link" do
      assign(:item, stub_model(Item, user: nil))
      render
      rendered.should_not have_content("Hello!")
    end
  end
end

This clones my fork and also adds the parent as the upstream remote.

cd ~
git clone git@github.com:jgeiger/vim-config.git ~/.vim
cd ~/.vim
git submodule update --init
ln -s ~/.vim/vimrc ~/.vimrc
git remote add upstream https://github.com/Casecommons/vim-config.git

Now if you add this to your .gitconfig you can do an easy git pu to pull in changes from both branches.

[alias]
  pu = !"git fetch origin -v; git fetch upstream -v; git merge upstream/master"

Thanks
http://gitready.com/intermediate/2009/02/12/easily-fetching-upstream-changes.html

cd ~
git clone git@github.com:jgeiger/vim-config.git ~/.vim
cd ~/.vim
git submodule update --init
ln -s ~/.vim/vimrc ~/.vimrc
sudo mv /usr/bin/vim /usr/bin/vim72
brew install https://raw.github.com/Homebrew/homebrew-dupes/master/vim.rb
cd .vim/bundle/command-t/ruby/command-t/
/usr/bin/ruby extconf.rb

I’m using rbenv with ruby 1.9.3-p125 as my main ruby, but you need to make sure that you compile command-t against whatever ruby vim as compiled with. The homebrew-dupes forumla uses the system ruby (which lives at /usr/bin/ruby) and even if you have rbenv global set to another ruby, you can always directly use the system ruby.

Thanks to:
https://github.com/Casecommons/vim-config
https://github.com/Casecommons/casecommons_workstation/blob/master/recipes/vim.rb