<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Post-Mortem on Bridge</title><link>https://quarternotecoda.com/tags/post-mortem/</link><description>Recent content in Post-Mortem on Bridge</description><generator>Hugo -- 0.160.1</generator><language>en-us</language><lastBuildDate>Fri, 09 Aug 2013 00:00:00 +0000</lastBuildDate><atom:link href="https://quarternotecoda.com/tags/post-mortem/index.xml" rel="self" type="application/rss+xml"/><item><title>Pairing Post Mortem - @piisalie - Emacs and Exercism.io</title><link>https://quarternotecoda.com/posts/2013-08-09-pairing-post-mortem-at-piisalie-emacs-and-exercism-dot-io/</link><pubDate>Fri, 09 Aug 2013 00:00:00 +0000</pubDate><guid>https://quarternotecoda.com/posts/2013-08-09-pairing-post-mortem-at-piisalie-emacs-and-exercism-dot-io/</guid><description>&lt;p&gt;The other night, I got to pair with &lt;a href="http://twitter.com/piisalie"&gt;@piisalie&lt;/a&gt; to
learn some Emacs and work through a little &lt;a href="http://exercism.io"&gt;exercism.io&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Paul is a relatively new developer, but he&amp;rsquo;s been studying under the tutelage
of &lt;a href="http://twitter.com/jeg2"&gt;@jeg2&lt;/a&gt; and getting ramped up very quickly as a
result. It&amp;rsquo;s neat to see people who are able to absorb so much so quickly.&lt;/p&gt;
&lt;h3 id="setup"&gt;Setup&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Google+ Hangouts&lt;/li&gt;
&lt;li&gt;TMUX + Emacs (Ahhhhhhhhhhh!!)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Paul was pretty familiar with Emacs and did a good job showing me around. We
worked on a small exercise and I tried to do as much of the editing as possible
as he guided me when I said &amp;ldquo;how do I move up and down again?&amp;rdquo;&lt;/p&gt;</description></item><item><title>Pairing Post Mortem - @jnanney - OAuth</title><link>https://quarternotecoda.com/posts/2013-07-18-pairing-post-mortem-at-jnanney-oauth/</link><pubDate>Thu, 18 Jul 2013 00:00:00 +0000</pubDate><guid>https://quarternotecoda.com/posts/2013-07-18-pairing-post-mortem-at-jnanney-oauth/</guid><description>&lt;p&gt;I finally got a chance to pair with &lt;a href="http://twitter.com/jnanney"&gt;@jnanney&lt;/a&gt; tonight. He had a project dealing with the OnStar API that needed OAuth Authentication, so we took a stab at implementing it.&lt;/p&gt;
&lt;h2 id="setup"&gt;Setup&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Skype - TIL Skype 6.x turns off your video if you connect to a Skype 2.0 client&amp;ndash;but the audio still works!&lt;/li&gt;
&lt;li&gt;TMUX+VIM on a slice (not local)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="experience"&gt;Experience&lt;/h2&gt;
&lt;p&gt;We started by making some large, rough ideas about what we wanted to accomplish and then began looking up some things on OAuth2 to help us accomplish them. Pretty quickly we stopped driving everything via tests and started exploring via &lt;code&gt;IRB&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>Pairing Post Mortem - @willpragnell - Mute Pairing with VIM</title><link>https://quarternotecoda.com/posts/2013-07-09-pairing-post-mortem-at-willpragnell-mute-pairing-with-vim/</link><pubDate>Tue, 09 Jul 2013 00:00:00 +0000</pubDate><guid>https://quarternotecoda.com/posts/2013-07-09-pairing-post-mortem-at-willpragnell-mute-pairing-with-vim/</guid><description>&lt;p&gt;Last week I had the opportunity to pair again with &lt;a href="http://twitter.com/willpragnell"&gt;@willpragnell&lt;/a&gt;. He had just moved and didn&amp;rsquo;t have internet access, so I suggested that we try a &amp;ldquo;mute&amp;rdquo; pairing session from a coffee shop, where all our communication happened through VIM.&lt;/p&gt;
&lt;p&gt;He was game, so we started off with a quick chat session on Google+ to get set up, and then switched to a VIM+TMUX setup for the rest of the time.&lt;/p&gt;</description></item><item><title>Pairing Post Mortem - @peter_v - Improving a Semantic Store</title><link>https://quarternotecoda.com/posts/2013-07-03-pairing-post-mortem-at-peter-v-improving-a-fact-engine/</link><pubDate>Wed, 03 Jul 2013 00:00:00 +0000</pubDate><guid>https://quarternotecoda.com/posts/2013-07-03-pairing-post-mortem-at-peter-v-improving-a-fact-engine/</guid><description>&lt;p&gt;Today I got to pair with &lt;a href="http://twitter.com/peter_v"&gt;Peter Vanderabeele&lt;/a&gt;, who is a programmer from Belgium with a highly methodical bent. He has clearly had a lot of experience and it was neat to get to work on his project since it isn&amp;rsquo;t every day you get to work on a high performance fact storage system.&lt;/p&gt;
&lt;p&gt;Peter is creating a data store meant to store semantic facts that have relationships to each other. It&amp;rsquo;s a very different project with a goal, he stated, to have data in this format and extractable for the next 50 years. To try to view code with that lens is very different from how most other Rubyists think. We tend to see our code dying in the next 5 years&amp;hellip; max. So we make decisions with that timeline in mind. Thinking of a timeline longer than my own life has very different implications.&lt;/p&gt;</description></item><item><title>Pairing Post Mortem - @stuartrexking - Cane Extension</title><link>https://quarternotecoda.com/posts/2013-06-29-pairing-post-mortem-at-stuartrexking-cane-extension/</link><pubDate>Mon, 24 Jun 2013 00:00:00 +0000</pubDate><guid>https://quarternotecoda.com/posts/2013-06-29-pairing-post-mortem-at-stuartrexking-cane-extension/</guid><description>&lt;p&gt;Last night&amp;rsquo;s pair session was with &lt;a href="http://twitter.com/stuartrexking"&gt;@stuartrexking&lt;/a&gt; - a very experienced developer and technologist currently working at a really neat company called &lt;a href="http://antipodeanlabs.com/"&gt;Antipodean Labs&lt;/a&gt;. It seems like he&amp;rsquo;s got a great handle on solving problems and staying maintainable.&lt;/p&gt;
&lt;p&gt;We started off by trying to decide what to do. I&amp;rsquo;m increasingly convinced this is the possibly the hardest part of remote pairing with people who aren&amp;rsquo;t part of your company. You don&amp;rsquo;t have a predefined complex project you both find interest in, so the most likely shared interests are either meta problems or highly common ones. Highly common ones are very visible and difficult to find low hanging fruit for. The meta problems are good to solve, but somehow feel like they are less valuable than the &amp;ldquo;real&amp;rdquo; problems. Maybe this is just a feeling I have.&lt;/p&gt;</description></item><item><title>Pairing Post Mortem - @_zph - Meta Pull Requests</title><link>https://quarternotecoda.com/posts/2013-06-19-pairing-post-mortem-at-zph-meta-pull-requests/</link><pubDate>Wed, 19 Jun 2013 00:00:00 +0000</pubDate><guid>https://quarternotecoda.com/posts/2013-06-19-pairing-post-mortem-at-zph-meta-pull-requests/</guid><description>&lt;p&gt;I had a great &lt;a href="http://pairprogramwith.me"&gt;#pairwithme&lt;/a&gt; session with &lt;a href="http://twitter.com/_zph"&gt;@_zph&lt;/a&gt;. Always a pleasure to talk to him and solve a problem together.&lt;/p&gt;
&lt;h2 id="setup"&gt;Setup&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;TMUX + VIM on a slice&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/chrishunt/github-auth"&gt;github-auth&lt;/a&gt; gem&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="experience"&gt;Experience&lt;/h2&gt;
&lt;p&gt;We wanted to add the feature to &lt;code&gt;gh-auth&lt;/code&gt; so you could pass a &lt;code&gt;&amp;ndash;path&lt;/code&gt; or &lt;code&gt;&amp;ndash;user&lt;/code&gt; argument to it. Because we&amp;rsquo;re good developers, we started off by coding the acceptance test. We discussed the merits of how to write good tests and whether to follow convetions within a gem authored by someone else or do things &amp;rsquo;the right way&amp;rsquo; &amp;ndash; according to whatever coding religion you follow. Eventually we decided on sticking to the conventions of the gem while trying to improve&amp;ndash;but not radically change&amp;ndash;the tests/testing that we touched. From there, we dove down into the implementation and unit tests and drove through until we had the &lt;code&gt;&amp;ndash;path&lt;/code&gt; argument working. Along the way we did a little refactoring to use the &lt;a href="http://ruby-doc.org/stdlib-1.9.3/libdoc/optparse/rdoc/OptionParser.html"&gt;OptionParser&lt;/a&gt; instead of requiring a specific ordering of options.&lt;/p&gt;</description></item><item><title>Pairing Post Mortem - @Shicholas - String Calculator</title><link>https://quarternotecoda.com/posts/2013-06-18-pairing-post-mortem-at-shicholas-string-calculator/</link><pubDate>Tue, 18 Jun 2013 00:00:00 +0000</pubDate><guid>https://quarternotecoda.com/posts/2013-06-18-pairing-post-mortem-at-shicholas-string-calculator/</guid><description>&lt;p&gt;Last night I had a great pairing with &lt;a href="http://twitter.com/Schicholas"&gt;@Shicholas&lt;/a&gt; working on the &lt;a href="http://osherove.com/tdd-kata-1/"&gt;String Calculator kata&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id="setup"&gt;Setup&lt;/h2&gt;
&lt;p&gt;We again used TMUX + VIM, even though Nick wasn&amp;rsquo;t very familiar with VIM. Based on his experience, I think this might be the &lt;strong&gt;best way to learn VIM&lt;/strong&gt; since you have someone guiding you through. You won&amp;rsquo;t pick up on everything, but you&amp;rsquo;ll learn a handful of new things each time.&lt;/p&gt;
&lt;h2 id="exercise"&gt;Exercise&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://gist.github.com/marksim/5802445"&gt;We went through each of the different rules and ping ponged back and forth&lt;/a&gt;. It was a struggle to do the &lt;em&gt;simplest&lt;/em&gt; possible thing every time, and really let the tests DRIVE your development. Your developer brain wants to generalize the solution to a problem, but the strength of TDD is keeping your &lt;em&gt;actual&lt;/em&gt; solution as simple as possible. Developers are notorious for over complicating things and over desigining.&lt;/p&gt;</description></item><item><title>Pairing Post Mortem - @hinbody - Attacking Open Source is Hard</title><link>https://quarternotecoda.com/posts/2013-06-14-pairing-post-mortem-at-hinbody-how-to-attack-open-source-projects/</link><pubDate>Fri, 14 Jun 2013 00:00:00 +0000</pubDate><guid>https://quarternotecoda.com/posts/2013-06-14-pairing-post-mortem-at-hinbody-how-to-attack-open-source-projects/</guid><description>&lt;p&gt;The easiest things to pair on are little tasks that you both understand and can be easily &amp;ldquo;completed&amp;rdquo; within a 1-2 hour pairing session. Unfortunately, Tic Tac Toe, Conway&amp;rsquo;s Game of Life and Bowling become stale quickly. It&amp;rsquo;s not that they don&amp;rsquo;t have valuable things to teach you, but you can&amp;rsquo;t pair with the same people over and over again just doing those problems. Eventually you need to dive into a real project.&lt;/p&gt;</description></item><item><title>Pairing Post Mortem - @willpragnell - Overseas TDD</title><link>https://quarternotecoda.com/posts/2013-06-14-pairing-post-mortem-at-willpragnell-overseas-tdd/</link><pubDate>Fri, 14 Jun 2013 00:00:00 +0000</pubDate><guid>https://quarternotecoda.com/posts/2013-06-14-pairing-post-mortem-at-willpragnell-overseas-tdd/</guid><description>&lt;p&gt;I had my first pairing session with &lt;a href="http://twitter.com/willpragnell"&gt;@willpragnell&lt;/a&gt; today. He&amp;rsquo;s a smart guy and my first European pair partner. It was a pleasure to talk to him about his iOS and Ruby experience and I picked up on a lot of little things from our pairing session together.&lt;/p&gt;
&lt;h2 id="setup"&gt;Setup&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;TMUX and VIM - (I got to use my &lt;a href="https://gist.github.com/marksim/5785406"&gt;newly revised pairing script&lt;/a&gt; to set up everything in seconds)&lt;/li&gt;
&lt;li&gt;TicTacToe - RSpec&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="the-session"&gt;The Session&lt;/h2&gt;
&lt;p&gt;We set a couple of goals out for the beginning. We both wanted to learn more of RSpec&amp;rsquo;s new syntax and we wanted to really adhear to the TDD principle of doing the most simple thing next.&lt;/p&gt;</description></item><item><title>Pairing Post Mortem - @mattr_ - Pending Specs and Assertions First</title><link>https://quarternotecoda.com/posts/2013-06-06-pairing-post-mortem-at-mattr-pending-specs-and-assertions-first/</link><pubDate>Thu, 06 Jun 2013 00:00:00 +0000</pubDate><guid>https://quarternotecoda.com/posts/2013-06-06-pairing-post-mortem-at-mattr-pending-specs-and-assertions-first/</guid><description>&lt;p&gt;Today I paired with &lt;a href="http://twitter.com/@mattr_"&gt;@mattr_&lt;/a&gt; and got quite a bit of good input regarding how to attack a problem and write tests. Matt is a super smart guy who has really absorbed some of the fundamentals of TDD and it shows through his ability to break down a problem.&lt;/p&gt;
&lt;h2 id="setup"&gt;Setup&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;TMUX &amp;amp; VIM on my box&lt;/li&gt;
&lt;li&gt;Conway&amp;rsquo;s Game of Life as an exercise&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="process"&gt;Process&lt;/h2&gt;
&lt;p&gt;When &lt;a href="https://gist.github.com/marksim/5723610"&gt;implementing the game of life&lt;/a&gt;, we started off looking at the problem on Wikipedia and found the 4 rules. I immediately started writing the first test when Matt noted that he liked to write all the specs he knows of as pending specs right at the beginning. Then he can really plow forward and know what&amp;rsquo;s next. He also noted that he likes to be able to write the assertion first, based on the test, and then build the test up from there. I felt the lightbulb go off when he pointed these two things out. When I&amp;rsquo;ve struggled to find the test or figure out how to test something, usually it&amp;rsquo;s because I can&amp;rsquo;t figure out how to get to the assertion, and that really comes down to not testing the right thing.&lt;/p&gt;</description></item><item><title>Pairing Post Mortem - The Mistake</title><link>https://quarternotecoda.com/posts/2013-06-06-pairing-post-mortem-the-mistake/</link><pubDate>Thu, 06 Jun 2013 00:00:00 +0000</pubDate><guid>https://quarternotecoda.com/posts/2013-06-06-pairing-post-mortem-the-mistake/</guid><description>&lt;p&gt;{% blockquote Chris Knight and Lazlo Holyfeld &lt;a href="http://www.imdb.com/title/tt0089886/trivia?item=qt0435761"&gt;http://www.imdb.com/title/tt0089886/trivia?item=qt0435761&lt;/a&gt; Real Genius %}
&amp;ldquo;How&amp;rsquo;d I do? I passed! But I failed! Yeah!&amp;rdquo;
&amp;ldquo;Well, then I&amp;rsquo;m happy and sad for you.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Last night I made a mistake. In an effort to continue pairing with people I really enjoyed pairing with, I scheduled 2 pairing sessions for the same evening. I left 30 minutes between them, I prepared as I should&amp;hellip; but I was stressed and it made both sessions worse.&lt;/p&gt;</description></item><item><title>Pairing Post Mortem - @_zph - VIM and a Gem</title><link>https://quarternotecoda.com/posts/2013-06-05-pairing-post-mortem-at-zph-vim-and-a-gem/</link><pubDate>Wed, 05 Jun 2013 00:00:00 +0000</pubDate><guid>https://quarternotecoda.com/posts/2013-06-05-pairing-post-mortem-at-zph-vim-and-a-gem/</guid><description>&lt;p&gt;Last night I had a great &lt;a href="http://pairprogramwith.me"&gt;#pairwithme&lt;/a&gt; session with &lt;a href="http://twitter.com/_zph"&gt;@_zph&lt;/a&gt;. He&amp;rsquo;s been doing Ruby on nights and weekends for the last few years and he&amp;rsquo;s been using &lt;a href="http://www.vim.org"&gt;VIM&lt;/a&gt; much longer than I have. I learned a lot of little tricks about VIM that I just hadn&amp;rsquo;t quite worked out before. We also refactored some of his &lt;a href="http://github.com/zph/buff"&gt;Buff&lt;/a&gt; Gem.&lt;/p&gt;
&lt;p&gt;Setup:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Zander had a VPS already provisioned with my ssh keys installed. Super Easy setup.&lt;/li&gt;
&lt;li&gt;TMUX + VIM for our editors&lt;/li&gt;
&lt;li&gt;RSpec for testing the Gem&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We started off trying to think of what to pair on within Zander&amp;rsquo;s gem. He was concerned about the tests, so we actually spent a fair amount of time just looking at the WebMocked tests and discussing the pros and cons. Eventually we decided that WebMock might be a good way to start off your TDD of an API wrapper since you have complete control of the response, but VCR gives you the best long term support since you can both get fast tests and confirm that you&amp;rsquo;re still working with the API correctly and that you didn&amp;rsquo;t just magically stub out the wrong thing&amp;ndash;just delete your cassette and you&amp;rsquo;ve got &amp;ldquo;free&amp;rdquo; real API tests, followed by nice fast tests.&lt;/p&gt;</description></item><item><title>Pairing Post Mortem - @Shicholas - Real World Lessons and Bowling</title><link>https://quarternotecoda.com/posts/2013-06-04-pairing-post-mortem-at-shicholas-angular-dot-js-and-bowling/</link><pubDate>Tue, 04 Jun 2013 00:00:00 +0000</pubDate><guid>https://quarternotecoda.com/posts/2013-06-04-pairing-post-mortem-at-shicholas-angular-dot-js-and-bowling/</guid><description>&lt;p&gt;Last night I had my first pairing session with &lt;a href="http://twitter.com/shicholas"&gt;@shicholas&lt;/a&gt;. Nick recently graduated from law school and is looking to pass the bar, but somehow programming calls to him. It&amp;rsquo;s a good thing too, since he&amp;rsquo;s clearly gifted and a fast learner.&lt;/p&gt;
&lt;p&gt;Setup:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ScreenHero&lt;/li&gt;
&lt;li&gt;Sublime Text 2&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/jarhart/shuhari"&gt;shuhari&lt;/a&gt; by &lt;a href="http://twitter.com/jarhart"&gt;@jarhart&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;While we were kicking things off with the &amp;ldquo;get to know you&amp;rdquo; talk, I found that Nick had a Rails + &lt;a href="http://angularjs.org/"&gt;Angular.js&lt;/a&gt; app he was working on. I&amp;rsquo;ve not done any work with Angular and asked him to show me what was going on. He pointed out the general structure as well as the custom &lt;em&gt;directives&lt;/em&gt; that Angular.js allows you to create. I&amp;rsquo;ve watched the &lt;a href="https://peepcode.com/products/emberjs"&gt;Ember.js Peepcode Intro&lt;/a&gt;, and found it difficult to get excited about it. Being introduced to Angular.js in this particular manner gave me real world applications and it seemed much more intriguing. No verdict yet on either, just initial impressions on both frameworks.&lt;/p&gt;</description></item><item><title>Pairing Post Mortem - @kmeister2000 - Refactoring and MiniTest</title><link>https://quarternotecoda.com/posts/2013-05-29-pairing-post-mortem-at-kmeister-refactoring-and-minitest/</link><pubDate>Wed, 29 May 2013 00:00:00 +0000</pubDate><guid>https://quarternotecoda.com/posts/2013-05-29-pairing-post-mortem-at-kmeister-refactoring-and-minitest/</guid><description>&lt;p&gt;Had a great 4th pairing with &lt;a href="http://twitter.com/kmeister2000"&gt;@kmeister2000&lt;/a&gt;. Always a pleasure to work with him.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Interesting Parts of our session setup:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Worked on a real world app Karl was developing&lt;/li&gt;
&lt;li&gt;Used MiniTest instead of RSpec&lt;/li&gt;
&lt;li&gt;Refactored existing code&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;MiniTest Takeaways:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;MiniTest expectations about method calls are not as clear as in Rspec and the documentation/examples aren&amp;rsquo;t as readily available.&lt;/li&gt;
&lt;li&gt;MiniTest is a lot like RSpec in nearly every other way.&lt;/li&gt;
&lt;li&gt;I&amp;rsquo;m not a fan of Mocha. I think it promotes antipatterns for how to really test.&lt;/li&gt;
&lt;li&gt;I actually like the explicit &lt;code&gt;mock.verify&lt;/code&gt; in MiniTest::Spec&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;General Takeaways:&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Pairing Post Mortem : @hinbody - TicTacToe and TMUX</title><link>https://quarternotecoda.com/posts/2013-05-29-pairing-post-mortem-at-hinbody-tictactoe-and-tmux/</link><pubDate>Wed, 29 May 2013 00:00:00 +0000</pubDate><guid>https://quarternotecoda.com/posts/2013-05-29-pairing-post-mortem-at-hinbody-tictactoe-and-tmux/</guid><description>&lt;p&gt;I just finished my first &lt;a href="https://twitter.com/search?q=%23pairwithme"&gt;#pairwithme&lt;/a&gt; session with &lt;a href="http://twitter.com/hinbody"&gt;@hinbody&lt;/a&gt;. It was my first remote session to use TMUX+VIM instead of ScreenHero &amp;ndash; I have to say, it was quite easy to use and given the fact that it&amp;rsquo;s &lt;em&gt;free&lt;/em&gt;, &lt;em&gt;fast&lt;/em&gt;, and &lt;em&gt;cross-platform&lt;/em&gt;, I&amp;rsquo;ll be using it with any vim users I pair with who are willing. I&amp;rsquo;d &lt;em&gt;love&lt;/em&gt; to get &lt;a href="https://github.com/FredKSchott/CoVim"&gt;CoVim&lt;/a&gt; working since it allows you to use your own vim setup. I drool a little bit at all that. But I digress.&lt;/p&gt;</description></item><item><title>Pairing Post Mortem : @thecommongeek - Ruby Koans</title><link>https://quarternotecoda.com/posts/2013-05-28-pairing-post-mortem-at-thecommongeek-ruby-koans/</link><pubDate>Tue, 28 May 2013 00:00:00 +0000</pubDate><guid>https://quarternotecoda.com/posts/2013-05-28-pairing-post-mortem-at-thecommongeek-ruby-koans/</guid><description>&lt;p&gt;I paired with &lt;a href="http://twitter.com/thecommongeek"&gt;@thecommongeek&lt;/a&gt; last night again. This time we were more prepared and I think the session went much better.&lt;/p&gt;
&lt;p&gt;In our &lt;a href="https://quarternotecoda.com/blog/2013/05/13/pairing-as-mentoring-first-impressions/"&gt;first session&lt;/a&gt; I misjudged where Dennis was as a coder and struggled a bit with how to pair with him effectively. This time we had him drive through &lt;a href="http://screenhero.com"&gt;ScreenHero&lt;/a&gt; and decided to start from the &amp;ldquo;basics&amp;rdquo; by doing the &lt;a href="http://rubykoans.com"&gt;RubyKoans&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The RubyKoans are meant for Ruby 1.8.7, but 1.9.3 is commonplace now, so we struggled a bit at the beginning. For anyone going through the RubyKoans on 1.9.3 getting a &lt;code&gt;value19&lt;/code&gt; in nearly all your errors, I&amp;rsquo;d suggest making the following changes on neo.rb (starting on line 34):&lt;/p&gt;</description></item><item><title>Pairing Post Mortem - @javichitone - Improving a Gem</title><link>https://quarternotecoda.com/posts/2013-05-22-pairing-post-mortem-at-javichitone-improving-a-gem/</link><pubDate>Wed, 22 May 2013 00:00:00 +0000</pubDate><guid>https://quarternotecoda.com/posts/2013-05-22-pairing-post-mortem-at-javichitone-improving-a-gem/</guid><description>&lt;p&gt;I had my first international pairing session with &lt;a href="http://twitter.com/javichitone"&gt;@javichitone&lt;/a&gt; tonight. He&amp;rsquo;s from Peru and will soon be graduating. He should have no trouble finding a job based on the code I got to read of his :)&lt;/p&gt;
&lt;p&gt;We talked for a bit and settled into looking at a gem he recently published. Since it was his gem, I elected to drive. I&amp;rsquo;m familiar enough with gems that I&amp;rsquo;m comfortable in &lt;em&gt;general&lt;/em&gt;, but he knew the &lt;em&gt;specifics&lt;/em&gt; of his gem, so to get the most out of it, he needed to be commenting on the specifics he knew and I needed to be diving into figuring out those specifics.&lt;/p&gt;</description></item><item><title>Pairing Post Mortem - @jdar - Chrome Extensions</title><link>https://quarternotecoda.com/posts/2013-05-21-pairing-post-mortem-at-jdar-on-chrome-extensions/</link><pubDate>Tue, 21 May 2013 00:00:00 +0000</pubDate><guid>https://quarternotecoda.com/posts/2013-05-21-pairing-post-mortem-at-jdar-on-chrome-extensions/</guid><description>&lt;p&gt;Another great pairing session tonight with &lt;a href="http://twitter.com/jdar"&gt;@jdar&lt;/a&gt;! I continue to be amazed at how pleasant and personable the developers I meet are. The internet is a wonderful place.&lt;/p&gt;
&lt;p&gt;First up, I&amp;rsquo;d never coded a Chrome Extension, so Darius took the reigns and started walking through what we were using. The biggest takeaway I got was to put your pride away when you&amp;rsquo;re pairing. Everyone&amp;rsquo;s exploring, we&amp;rsquo;re all trying to get to the next answer, so it doesn&amp;rsquo;t matter if we&amp;rsquo;re really well prepared or never coded before&amp;hellip; just take the next step.&lt;/p&gt;</description></item><item><title>Pairing Post Mortem - @kmeister2000 - TDD and Domain Knowledge</title><link>https://quarternotecoda.com/posts/2013-05-16-pairing-post-mortem-at-kmeister2000/</link><pubDate>Thu, 16 May 2013 00:00:00 +0000</pubDate><guid>https://quarternotecoda.com/posts/2013-05-16-pairing-post-mortem-at-kmeister2000/</guid><description>&lt;p&gt;Last night I did a &lt;a href="http://pairprogramwith.me"&gt;#pairwithme&lt;/a&gt; session with Karl Meisterheim. He&amp;rsquo;s an experienced developer who currently work part time and was looking to improve his skills. Besides having a good deal in common and really enjoying our conversation, I also learned a bit more about remote pairing and came away with a couple of observations.&lt;/p&gt;
&lt;p&gt;First off, we paired 2 nights in a row for about an hour each night. Both sessions we tried to solve the same problem: TicTacToe. We started off on the second night with the code from the first night, but quickly threw it away and decided to &amp;ldquo;start over&amp;rdquo; as an excercise. Doing this taught me the most significant lessons from our session.&lt;/p&gt;</description></item><item><title>Pairing Post Mortem - @thecommongeek - Learning and Mentoring</title><link>https://quarternotecoda.com/posts/2013-05-13-pairing-as-mentoring-first-impressions/</link><pubDate>Mon, 13 May 2013 00:00:00 +0000</pubDate><guid>https://quarternotecoda.com/posts/2013-05-13-pairing-as-mentoring-first-impressions/</guid><description>&lt;p&gt;I had a great pairing session with &lt;a href="http://twitter.com/thecommongeek"&gt;@thecommongeek&lt;/a&gt; tonight. It was my first live-remote pair programming and I wanted to to a little &amp;ldquo;post mortem&amp;rdquo; on it to record my thoughts.&lt;/p&gt;
&lt;p&gt;We spent some time on introductions and then jumped into a problem. Since my box was all set up, I typed. I&amp;rsquo;m more experienced than Dennis as a coder, so I viewed it as the potential to mentor him a bit. I also learned from him both in the &amp;ldquo;how to be a better mentor&amp;rdquo; department and the &amp;ldquo;how to pair better&amp;rdquo; department.&lt;/p&gt;</description></item></channel></rss>