<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>@benmatselby</title>
	<atom:link href="http://www.soulbroken.co.uk/blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.soulbroken.co.uk/blog</link>
	<description>Just another manic monday</description>
	<lastBuildDate>Thu, 03 May 2012 14:45:55 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>pman for Sublime Text 2</title>
		<link>http://www.soulbroken.co.uk/blog/2012/04/pman-for-sublime-text-2/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=pman-for-sublime-text-2</link>
		<comments>http://www.soulbroken.co.uk/blog/2012/04/pman-for-sublime-text-2/#comments</comments>
		<pubDate>Mon, 09 Apr 2012 08:57:49 +0000</pubDate>
		<dc:creator>benmatselby</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[plugins]]></category>
		<category><![CDATA[pman]]></category>
		<category><![CDATA[python]]></category>
		<category><![CDATA[sublimetext2]]></category>

		<guid isPermaLink="false">http://www.soulbroken.co.uk/blog/?p=287</guid>
		<description><![CDATA[Sometimes you simply don&#8217;t have access to the internet, maybe you&#8217;re on a train and have no wifi, or are unwilling to pay such extortionate prices. So what would you do when you need the php manual? Hopefully you have installed pman, &#8230; <a href="http://www.soulbroken.co.uk/blog/2012/04/pman-for-sublime-text-2/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.soulbroken.co.uk/blog/2012/04/pman-for-sublime-text-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Jenkins as Project Maintainer</title>
		<link>http://www.soulbroken.co.uk/blog/2012/04/jenkins-as-project-maintainer/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=jenkins-as-project-maintainer</link>
		<comments>http://www.soulbroken.co.uk/blog/2012/04/jenkins-as-project-maintainer/#comments</comments>
		<pubDate>Sun, 01 Apr 2012 19:30:18 +0000</pubDate>
		<dc:creator>benmatselby</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[automation]]></category>
		<category><![CDATA[continuousintegration]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[jenkins]]></category>
		<category><![CDATA[projectmanagement]]></category>
		<category><![CDATA[work]]></category>

		<guid isPermaLink="false">http://www.soulbroken.co.uk/blog/?p=261</guid>
		<description><![CDATA[I remember not so long back (about 8 months), when we use to have project leads looking after all the git repos touched for a given project. They were the only ones who could push to the project repo (bottleneck) &#8230; <a href="http://www.soulbroken.co.uk/blog/2012/04/jenkins-as-project-maintainer/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.soulbroken.co.uk/blog/2012/04/jenkins-as-project-maintainer/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Sublime DocBlox Plugin Renamed to Sublime phpDocumentor</title>
		<link>http://www.soulbroken.co.uk/blog/2012/03/sublime-docblox-plugin-renamed-to-sublime-phpdocumentor/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=sublime-docblox-plugin-renamed-to-sublime-phpdocumentor</link>
		<comments>http://www.soulbroken.co.uk/blog/2012/03/sublime-docblox-plugin-renamed-to-sublime-phpdocumentor/#comments</comments>
		<pubDate>Fri, 16 Mar 2012 22:47:52 +0000</pubDate>
		<dc:creator>benmatselby</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[docblox]]></category>
		<category><![CDATA[phpdocumentor]]></category>
		<category><![CDATA[sublimetext2]]></category>

		<guid isPermaLink="false">http://www.soulbroken.co.uk/blog/?p=269</guid>
		<description><![CDATA[In relation to the news that DocBlox has merged with phpDoc to form phpDocumentor 2, I&#8217;ve updated/renamed the DocBlox Plugin For Sublime Text 2 to phpDocumentor Plugin For Sublime Text 2.. See what I did there? There is currently a pull &#8230; <a href="http://www.soulbroken.co.uk/blog/2012/03/sublime-docblox-plugin-renamed-to-sublime-phpdocumentor/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.soulbroken.co.uk/blog/2012/03/sublime-docblox-plugin-renamed-to-sublime-phpdocumentor/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Installed Sublime Test 2 Plugins</title>
		<link>http://www.soulbroken.co.uk/blog/2012/03/installed-sublime-test-2-plugins/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=installed-sublime-test-2-plugins</link>
		<comments>http://www.soulbroken.co.uk/blog/2012/03/installed-sublime-test-2-plugins/#comments</comments>
		<pubDate>Tue, 13 Mar 2012 20:00:38 +0000</pubDate>
		<dc:creator>benmatselby</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[ide]]></category>
		<category><![CDATA[sublimetext2]]></category>
		<category><![CDATA[thoughts]]></category>

		<guid isPermaLink="false">http://www.soulbroken.co.uk/blog/?p=246</guid>
		<description><![CDATA[This post is more for me than anything else.. I just need a reference point for all the Sublime Test 2 Plugins I am using. So here goes: Package Control - The one plugin to rule them all. This Plugin helps &#8230; <a href="http://www.soulbroken.co.uk/blog/2012/03/installed-sublime-test-2-plugins/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.soulbroken.co.uk/blog/2012/03/installed-sublime-test-2-plugins/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PHP_CodeSniffer Plugin For Sublime Text 2</title>
		<link>http://www.soulbroken.co.uk/blog/2012/02/php_codesniffer-plugin-for-sublime-text-2/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=php_codesniffer-plugin-for-sublime-text-2</link>
		<comments>http://www.soulbroken.co.uk/blog/2012/02/php_codesniffer-plugin-for-sublime-text-2/#comments</comments>
		<pubDate>Mon, 13 Feb 2012 13:04:58 +0000</pubDate>
		<dc:creator>benmatselby</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[phpcs]]></category>
		<category><![CDATA[sublimetext2]]></category>
		<category><![CDATA[technical]]></category>

		<guid isPermaLink="false">http://www.soulbroken.co.uk/blog/?p=221</guid>
		<description><![CDATA[On the heels of the DocBlox Plugin for Sublime Text 2 I&#8217;ve knocked up another plugin, this time for PHP_CodeSniffer. This plugin is a little more integrated and intelligent than the last one. This can run the code sniffer and php &#8230; <a href="http://www.soulbroken.co.uk/blog/2012/02/php_codesniffer-plugin-for-sublime-text-2/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.soulbroken.co.uk/blog/2012/02/php_codesniffer-plugin-for-sublime-text-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>DocBlox/phpDocumentor Plugin For Sublime Text 2</title>
		<link>http://www.soulbroken.co.uk/blog/2012/02/docblox-plugin-for-sublime-text-2/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=docblox-plugin-for-sublime-text-2</link>
		<comments>http://www.soulbroken.co.uk/blog/2012/02/docblox-plugin-for-sublime-text-2/#comments</comments>
		<pubDate>Mon, 06 Feb 2012 12:20:39 +0000</pubDate>
		<dc:creator>benmatselby</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[docblox]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[sublimetext2]]></category>

		<guid isPermaLink="false">http://www.soulbroken.co.uk/blog/?p=190</guid>
		<description><![CDATA[Edit: This plugin is now renamed to sublime phpdocumentor due to DocBlox being merged with phpdoc It seems that the editor of the moment is Sublime Text 2 and sadly I have to tip my hat to Gary Rockett for &#8230; <a href="http://www.soulbroken.co.uk/blog/2012/02/docblox-plugin-for-sublime-text-2/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.soulbroken.co.uk/blog/2012/02/docblox-plugin-for-sublime-text-2/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Don&#8217;t just fix the unit tests!</title>
		<link>http://www.soulbroken.co.uk/blog/2012/02/dont-just-fix-the-unit-tests/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=dont-just-fix-the-unit-tests</link>
		<comments>http://www.soulbroken.co.uk/blog/2012/02/dont-just-fix-the-unit-tests/#comments</comments>
		<pubDate>Sun, 05 Feb 2012 09:33:06 +0000</pubDate>
		<dc:creator>benmatselby</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[technical]]></category>
		<category><![CDATA[unit testing]]></category>
		<category><![CDATA[work]]></category>

		<guid isPermaLink="false">http://www.soulbroken.co.uk/blog/?p=168</guid>
		<description><![CDATA[I&#8217;m not sure if other people have had the same issue, but I see more and more developers &#8220;fixing the unit tests&#8221;, rather than understanding why they are broken and the business requirement they were originally testing. The problem use &#8230; <a href="http://www.soulbroken.co.uk/blog/2012/02/dont-just-fix-the-unit-tests/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.soulbroken.co.uk/blog/2012/02/dont-just-fix-the-unit-tests/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MongoDB PHPUnit Test Listener</title>
		<link>http://www.soulbroken.co.uk/blog/2012/02/mongodb-phpunit-test-listener/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=mongodb-phpunit-test-listener</link>
		<comments>http://www.soulbroken.co.uk/blog/2012/02/mongodb-phpunit-test-listener/#comments</comments>
		<pubDate>Fri, 03 Feb 2012 08:44:41 +0000</pubDate>
		<dc:creator>benmatselby</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[jenkins]]></category>
		<category><![CDATA[mongodb]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[phpunit]]></category>

		<guid isPermaLink="false">http://www.soulbroken.co.uk/blog/?p=175</guid>
		<description><![CDATA[I&#8217;ve wanted to look into MongoDB for some time now, but never got the chance until this week. I decided to write a PHPUnit Test listener that could persist some of the test executions I was running locally so I could &#8230; <a href="http://www.soulbroken.co.uk/blog/2012/02/mongodb-phpunit-test-listener/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.soulbroken.co.uk/blog/2012/02/mongodb-phpunit-test-listener/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Use version control commit messages correctly</title>
		<link>http://www.soulbroken.co.uk/blog/2012/02/use-version-control-commit-messages-correctly/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=use-version-control-commit-messages-correctly</link>
		<comments>http://www.soulbroken.co.uk/blog/2012/02/use-version-control-commit-messages-correctly/#comments</comments>
		<pubDate>Thu, 02 Feb 2012 13:16:01 +0000</pubDate>
		<dc:creator>benmatselby</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[codereviews]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[technical]]></category>

		<guid isPermaLink="false">http://www.soulbroken.co.uk/blog/?p=170</guid>
		<description><![CDATA[This post represents a conversation I&#8217;ve had multiple times with the dev teams I am involved with, and it doesn&#8217;t seem to get any better. I&#8217;ve &#8220;vented&#8221; at my wife, who has to listen (It said so in the vows!) &#8230; <a href="http://www.soulbroken.co.uk/blog/2012/02/use-version-control-commit-messages-correctly/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.soulbroken.co.uk/blog/2012/02/use-version-control-commit-messages-correctly/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Apple replace 1st generation iPod</title>
		<link>http://www.soulbroken.co.uk/blog/2012/01/apple-replace-1st-generation-ipod/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=apple-replace-1st-generation-ipod</link>
		<comments>http://www.soulbroken.co.uk/blog/2012/01/apple-replace-1st-generation-ipod/#comments</comments>
		<pubDate>Thu, 05 Jan 2012 20:52:13 +0000</pubDate>
		<dc:creator>benmatselby</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[apple]]></category>
		<category><![CDATA[life]]></category>

		<guid isPermaLink="false">http://www.soulbroken.co.uk/blog/?p=161</guid>
		<description><![CDATA[My wife was lucky enough to get a 1st generation iPod nano for Christmas 6 years ago from her then, loving boyfriend. We loved that little white iPod nano, and in the end it spent it&#8217;s days in the iPod &#8230; <a href="http://www.soulbroken.co.uk/blog/2012/01/apple-replace-1st-generation-ipod/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.soulbroken.co.uk/blog/2012/01/apple-replace-1st-generation-ipod/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

