<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.9.2" -->
<rss version="0.92">
<channel>
	<title>Kerry Buckley</title>
	<link>http://www.kerrybuckley.org</link>
	<description>What's the simplest thing that could possibly go wrong?</description>
	<lastBuildDate>Tue, 03 Nov 2009 11:21:24 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>Managing gems in a Rails project</title>
		<description><![CDATA[Over the years I've tried a number of approaches for managing gem dependencies in a Rails project. Here's a quick round-up of what I've tried, and the pros and cons of each.
Just use what's on the system
This is probably most people's default approach when first starting with Rails. Just sudo gem install whatever you need, [...]]]></description>
		<link>http://www.kerrybuckley.org/2009/11/02/managing-gems-in-a-rails-project/</link>
			</item>
	<item>
		<title>Maintaining a Read-Only svn Mirror of a git Repository</title>
		<description><![CDATA[Our team been using git at work for the past couple of years, but there's now a corporate push to keep everything in a centrally-managed subversion repository. We lost the battle to get corporate approval for git (apparently we're happy to employ people to write our code that we wouldn't trust to be able to [...]]]></description>
		<link>http://www.kerrybuckley.org/2009/10/06/maintaining-a-read-only-svn-mirror-of-a-git-repository/</link>
			</item>
	<item>
		<title>Upgrading to Snow Leopard</title>
		<description><![CDATA[A quick list of things I had to sort out after upgrading to Mac OS X 10.6 Snow Leopard:
Developer Tools
Dont' forget to run the XCode installer on the Snow Leopard DVD, otherwise you'll have trouble getting stuff to compile, even if you don't use XCode. You'll also have to download and install the iPhone SDK [...]]]></description>
		<link>http://www.kerrybuckley.org/2009/09/09/upgrading-to-snow-leopard/</link>
			</item>
	<item>
		<title>Commenting broken</title>
		<description><![CDATA[Commenting seems to be broken on this blog since I upgraded WordPress. Not sure why yet, but I'm working on it.
[Update] It's working again now.
]]></description>
		<link>http://www.kerrybuckley.org/2009/08/15/commenting-broken/</link>
			</item>
	<item>
		<title>Comments aren&#8217;t always evil</title>
		<description><![CDATA[I tend to agree that comments are, in most cases, evil (or at least mildly malevolent), but I did come across one of the exceptions to the rule today.
While doing a bit of drive-by refactoring while fixing a bug, I reflexively changed this line:
PLAIN TEXT
RUBY:




unless instance_response.nil? 






to this:
PLAIN TEXT
RUBY:




if instance_response 






Then reading the comment above [...]]]></description>
		<link>http://www.kerrybuckley.org/2009/08/14/comments-arent-always-evil/</link>
			</item>
	<item>
		<title>Naresh Jain&#8217;s refactoring teaser</title>
		<description><![CDATA[Naresh Jain recently posted a refactoring teaser. The original code was in Java, but I thought I'd have a go at refactoring it in Ruby instead. I deliberately didn't look at Naresh's solution beforehand, so mine goes in a rather different direction.
My code's here (with the specs in the same file for simplicity), and you [...]]]></description>
		<link>http://www.kerrybuckley.org/2009/07/17/naresh-jains-refactoring-teaser/</link>
			</item>
	<item>
		<title>A couple of rspec mocking gotchas</title>
		<description><![CDATA[Just a couple of things that have caused a bit of head-scratching lately when writing RSpec specs using the built-in mocking framework.
Catching StandardError
Watch out if the code you're testing catches StandardError (of course you're not catching Exception, right?). Try this:
PLAIN TEXT
RUBY:




require 'rubygems'


require 'spec'


&#160;


class Foo


&#160; def self.foo


&#160; &#160; Bar.bar


&#160; rescue StandardError


&#160; &#160; # do something here [...]]]></description>
		<link>http://www.kerrybuckley.org/2009/05/28/a-couple-of-rspec-mocking-gotchas/</link>
			</item>
	<item>
		<title>Helpful message from rspec</title>
		<description><![CDATA[Just came across an interesting error message from rspec. I had a spec that looked like this:
PLAIN TEXT
RUBY:




it "should not mass-assign 'confirmed'" do


&#160; Blog.new&#40;:confirmed =&#62; true&#41;.confirmed.should_not be_true


end 






Obviously it failed, as I hadn't written the code yet, but there was more in the error message than I expected:
..........F

1)
RuntimeError in 'Blog should not mass-assign 'confirmed''
'should_not be [...]]]></description>
		<link>http://www.kerrybuckley.org/2009/05/04/helpful-message-from-rspec/</link>
			</item>
	<item>
		<title>Design by Example or Test-Driven Development?</title>
		<description><![CDATA[Brad Wilson argues the case for renaming TDD to 'Design by Example' (or DbE), to emphasise the fact that TDD (and BDD, which is really just TDD done well) are about design rather than testing.
I agree with the intention, but I'm not sure I agree. I'm happy to lose the 'test' &#038;ndash it's losing the [...]]]></description>
		<link>http://www.kerrybuckley.org/2009/04/28/design-by-example-or-test-driven-development/</link>
			</item>
	<item>
		<title>API vs RSI</title>
		<description><![CDATA[World's-most-famous-twitterer Stephen Fry has a system for handling follow requests: you tweet using the #followmestephen hashtag, and he wades diligently through them, manually following people.
This seems an odd sort of thing to do &#8211; most people choose whom to follow based on whether they know them or like what they say, rather than on request [...]]]></description>
		<link>http://www.kerrybuckley.org/2009/03/15/api-vs-rsi/</link>
			</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.549 seconds -->
