<?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>Barbary Codes and DataBarbary Codes and Data</title>
	<atom:link href="http://www.barbarycodes.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.barbarycodes.com</link>
	<description>Web and Mobile Development for Lean Startups</description>
	<lastBuildDate>Tue, 03 Apr 2012 17:51:33 +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>Fix for “git push” timeouts on new repository</title>
		<link>http://www.barbarycodes.com/2011/01/16/fix-for-%e2%80%9cgit-push%e2%80%9d-timeouts-on-new-repository/</link>
		<comments>http://www.barbarycodes.com/2011/01/16/fix-for-%e2%80%9cgit-push%e2%80%9d-timeouts-on-new-repository/#comments</comments>
		<pubDate>Mon, 17 Jan 2011 05:01:46 +0000</pubDate>
		<dc:creator>tjones@barbarycodes.com</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.barbarycodes.com/?p=255</guid>
		<description><![CDATA[While migrating a large codebase from Subversion to Git recently I ran across the following error during the initial push from my development system to the new remote repository: Read from remote host &#60;&#8230;&#62;: Operation timed out error: pack-objects died of signal 13 error: failed to push some refs to &#8216;ssh://&#60;&#8230;&#62;&#8217; Rerunning &#8220;git push&#8221; with&#8230; <a href="http://www.barbarycodes.com/2011/01/16/fix-for-%e2%80%9cgit-push%e2%80%9d-timeouts-on-new-repository/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.barbarycodes.com/2011/01/16/fix-for-%e2%80%9cgit-push%e2%80%9d-timeouts-on-new-repository/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>TextMate Pattern to Exclude Rails&#039; vendor Directory (most of the time)</title>
		<link>http://www.barbarycodes.com/2011/01/01/textmate-pattern-to-exclude-rails-vendor-directory-most-of-the-time/</link>
		<comments>http://www.barbarycodes.com/2011/01/01/textmate-pattern-to-exclude-rails-vendor-directory-most-of-the-time/#comments</comments>
		<pubDate>Sat, 01 Jan 2011 20:28:59 +0000</pubDate>
		<dc:creator>tjones@barbarycodes.com</dc:creator>
				<category><![CDATA[rails]]></category>
		<category><![CDATA[tools]]></category>

		<guid isPermaLink="false">http://timothynjones.wordpress.com/?p=141</guid>
		<description><![CDATA[It&#8217;s useful to (a) exclude the vendor directory from normal TextMate projects, but (b) still be able to pull up the Rails source under vendor/rails from time to time. If you simply add vendor to the TextMate Folder Pattern, you&#8217;ll get (a) but not (b). To get both, add vendor$. Here are the patterns I&#8230; <a href="http://www.barbarycodes.com/2011/01/01/textmate-pattern-to-exclude-rails-vendor-directory-most-of-the-time/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.barbarycodes.com/2011/01/01/textmate-pattern-to-exclude-rails-vendor-directory-most-of-the-time/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>All Ruby Code Should Use Explicit Returns (Especially With Rails)</title>
		<link>http://www.barbarycodes.com/2010/10/07/all-ruby-code-should-use-explicit-returns-especially-with-rails/</link>
		<comments>http://www.barbarycodes.com/2010/10/07/all-ruby-code-should-use-explicit-returns-especially-with-rails/#comments</comments>
		<pubDate>Thu, 07 Oct 2010 23:40:36 +0000</pubDate>
		<dc:creator>tjones@barbarycodes.com</dc:creator>
				<category><![CDATA[rails]]></category>
		<category><![CDATA[ruby]]></category>

		<guid isPermaLink="false">http://timothynjones.wordpress.com/?p=128</guid>
		<description><![CDATA[A lot of people who enter programming through hacking around with scripting languages rather than formal computer science educations don&#8217;t understand certain fundamentals such as the difference between functional and non-functional programming models (hint: Ruby isn&#8217;t functional). One of the Rails core team members argues that explicit return statements in Ruby code is a bad thing.&#8230; <a href="http://www.barbarycodes.com/2010/10/07/all-ruby-code-should-use-explicit-returns-especially-with-rails/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.barbarycodes.com/2010/10/07/all-ruby-code-should-use-explicit-returns-especially-with-rails/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Automated Banning of Script Kiddies with fail2ban</title>
		<link>http://www.barbarycodes.com/2010/10/06/automated-banning-of-script-kiddies-with-fail2ban/</link>
		<comments>http://www.barbarycodes.com/2010/10/06/automated-banning-of-script-kiddies-with-fail2ban/#comments</comments>
		<pubDate>Wed, 06 Oct 2010 22:54:19 +0000</pubDate>
		<dc:creator>tjones@barbarycodes.com</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[apache]]></category>
		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://timothynjones.wordpress.com/?p=121</guid>
		<description><![CDATA[I like to configure my webapps to automatically send me email upon any error, including 404s (file not found), since that can indicate a bad link within the app.  Unfortunately, script kiddies trying URLs like /phpMyAdmin/scripts/setup.php and hundreds of similar variants can trigger the email and flood my inbox. fail2ban to the rescue!  This wonderful tool&#8230; <a href="http://www.barbarycodes.com/2010/10/06/automated-banning-of-script-kiddies-with-fail2ban/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.barbarycodes.com/2010/10/06/automated-banning-of-script-kiddies-with-fail2ban/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Why I Switched From MySQL To Postgresql</title>
		<link>http://www.barbarycodes.com/2010/03/18/why-i-switched-from-mysql-to-postgresql/</link>
		<comments>http://www.barbarycodes.com/2010/03/18/why-i-switched-from-mysql-to-postgresql/#comments</comments>
		<pubDate>Fri, 19 Mar 2010 02:43:01 +0000</pubDate>
		<dc:creator>tjones@barbarycodes.com</dc:creator>
				<category><![CDATA[mysql]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://timothynjones.wordpress.com/?p=114</guid>
		<description><![CDATA[I&#8217;m working on a project which has a very &#8220;wide&#8221; database schema &#8212; not many rows, but lots and lots of (text) columns.  Since I use InnoDB exclusively on MySQL (due to its lack of constraints and transactions, MyISAM is not suitable for production use), I ran into the mysterious &#8220;error 139&#8243; when adding rows&#8230; <a href="http://www.barbarycodes.com/2010/03/18/why-i-switched-from-mysql-to-postgresql/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.barbarycodes.com/2010/03/18/why-i-switched-from-mysql-to-postgresql/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Ruby Class Attributes Are Not Thread Safe</title>
		<link>http://www.barbarycodes.com/2010/03/02/ruby-class-attributes-are-not-thread-safe/</link>
		<comments>http://www.barbarycodes.com/2010/03/02/ruby-class-attributes-are-not-thread-safe/#comments</comments>
		<pubDate>Tue, 02 Mar 2010 22:28:52 +0000</pubDate>
		<dc:creator>tjones@barbarycodes.com</dc:creator>
				<category><![CDATA[rails]]></category>

		<guid isPermaLink="false">http://timothynjones.wordpress.com/?p=109</guid>
		<description><![CDATA[Don&#8217;t use cattr_accessor, use Thread.current[].  Also note Rails bug 3457.]]></description>
		<wfw:commentRss>http://www.barbarycodes.com/2010/03/02/ruby-class-attributes-are-not-thread-safe/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How To Make $100 with MySQL REPEATABLE-READ Transactions</title>
		<link>http://www.barbarycodes.com/2010/02/18/how-to-make-100-with-mysql-repeatable-read-transactions/</link>
		<comments>http://www.barbarycodes.com/2010/02/18/how-to-make-100-with-mysql-repeatable-read-transactions/#comments</comments>
		<pubDate>Fri, 19 Feb 2010 02:31:49 +0000</pubDate>
		<dc:creator>tjones@barbarycodes.com</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[mysql]]></category>

		<guid isPermaLink="false">http://timothynjones.wordpress.com/?p=104</guid>
		<description><![CDATA[MySQL defaults to REPEATABLE-READ transactions.  This means that repeated SELECT statements within the same transaction return the same data (i.e., they don&#8217;t pick up interim updates made outside the transaction).  Specifically, reads take place from a snapshot of the database created for the first read in the transaction. This may lead to unexpected results when&#8230; <a href="http://www.barbarycodes.com/2010/02/18/how-to-make-100-with-mysql-repeatable-read-transactions/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.barbarycodes.com/2010/02/18/how-to-make-100-with-mysql-repeatable-read-transactions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Random Notes To Self Regarding ThinkingSphinx</title>
		<link>http://www.barbarycodes.com/2010/02/03/random-notes-to-self-regarding-thinkingsphinx/</link>
		<comments>http://www.barbarycodes.com/2010/02/03/random-notes-to-self-regarding-thinkingsphinx/#comments</comments>
		<pubDate>Thu, 04 Feb 2010 05:31:36 +0000</pubDate>
		<dc:creator>tjones@barbarycodes.com</dc:creator>
				<category><![CDATA[rails]]></category>

		<guid isPermaLink="false">http://timothynjones.wordpress.com/?p=100</guid>
		<description><![CDATA[You&#8217;re supposed to remember more of what you write, right? On ThinkingSphinx: Attributes are used for sorting, filtering and grouping your search results. Their values do not get paid any attention by Sphinx for search terms, though, and they’re limited to the following data types: integers, floats, datetimes (as Unix timestamps – and thus integers&#8230; <a href="http://www.barbarycodes.com/2010/02/03/random-notes-to-self-regarding-thinkingsphinx/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.barbarycodes.com/2010/02/03/random-notes-to-self-regarding-thinkingsphinx/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>FATAL bug in Capistrano 2.5.11</title>
		<link>http://www.barbarycodes.com/2010/01/04/fatal-bug-in-capistrano-2-5-11/</link>
		<comments>http://www.barbarycodes.com/2010/01/04/fatal-bug-in-capistrano-2-5-11/#comments</comments>
		<pubDate>Mon, 04 Jan 2010 22:55:32 +0000</pubDate>
		<dc:creator>tjones@barbarycodes.com</dc:creator>
				<category><![CDATA[ruby]]></category>

		<guid isPermaLink="false">http://timothynjones.wordpress.com/?p=96</guid>
		<description><![CDATA[This change to deploy.rb in Capistrano 2.5.11 is causing the deploy:cleanup task to REMOVE THE CURRENT VERSION OF THE APP FROM THE SERVER (at least under every version of Linux I&#8217;ve tried &#8212; maybe some other OS has other semantics for &#8220;ls -xt&#8221;).  I recommend reverting to 2.5.10 until this is fixed.]]></description>
		<wfw:commentRss>http://www.barbarycodes.com/2010/01/04/fatal-bug-in-capistrano-2-5-11/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Fix for Glassfish spontaneously exiting under Capistrano</title>
		<link>http://www.barbarycodes.com/2009/12/16/fix-for-glassfish-spontaneously-exiting-under-capistrano/</link>
		<comments>http://www.barbarycodes.com/2009/12/16/fix-for-glassfish-spontaneously-exiting-under-capistrano/#comments</comments>
		<pubDate>Wed, 16 Dec 2009 18:55:55 +0000</pubDate>
		<dc:creator>tjones@barbarycodes.com</dc:creator>
				<category><![CDATA[rails]]></category>

		<guid isPermaLink="false">http://timothynjones.wordpress.com/?p=93</guid>
		<description><![CDATA[I&#8217;m using Capistrano to deploy a Rails app running under JRuby via the Glassfish gem. For no apparent reason, the Glassfish Java process would exit immediately when started via Capistrano, but not when started via plain SSH or locally via the command line. I finally tracked this down to the following in my deploy.rb file:&#8230; <a href="http://www.barbarycodes.com/2009/12/16/fix-for-glassfish-spontaneously-exiting-under-capistrano/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://www.barbarycodes.com/2009/12/16/fix-for-glassfish-spontaneously-exiting-under-capistrano/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>

