<?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>my obsolete blog full of randomness &#187; dev and design</title>
	<atom:link href="http://archived.bradybouchard.ca/category/devanddesign/feed/" rel="self" type="application/rss+xml" />
	<link>http://archived.bradybouchard.ca</link>
	<description>Money can’t buy happiness. But it can buy marshmallows, which are kinda the same thing.</description>
	<lastBuildDate>Wed, 08 Sep 2010 16:07:22 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
<cloud domain='archived.bradybouchard.ca' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
		<item>
		<title>Using Rails Just Because</title>
		<link>http://archived.bradybouchard.ca/2008/07/using-rails-just-because/</link>
		<comments>http://archived.bradybouchard.ca/2008/07/using-rails-just-because/#comments</comments>
		<pubDate>Wed, 09 Jul 2008 15:13:05 +0000</pubDate>
		<dc:creator>brady</dc:creator>
				<category><![CDATA[dev and design]]></category>
		<category><![CDATA[web]]></category>
		<category><![CDATA[beast]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[forum software]]></category>
		<category><![CDATA[phpbb]]></category>
		<category><![CDATA[rails]]></category>
		<category><![CDATA[vanilla]]></category>

		<guid isPermaLink="false">http://blog.bradybouchard.ca/?p=53</guid>
		<description><![CDATA[There are many web development shops that are switching to Ruby on Rails, and this is generally a good thing &#8211; lots of new exposure to a great language, which means more tools and documentation and development by the growing community. Now, when a development studio switches to Rails, the one thing you shouldn&#8217;t do [...]]]></description>
			<content:encoded><![CDATA[<p>There are many web development shops that are switching to <a href="http://www.rubyonrails.org/">Ruby on Rails</a>, and this is generally a good thing &#8211; lots of new exposure to a great language, which means more tools and documentation and development by the growing community.</p>
<p>Now, when a development studio switches to Rails, the one thing you shouldn&#8217;t do is try your best to move all your tools over to Rails. Just because Rails is new and cool doesn&#8217;t mean that PHP and/or Perl and/or Python are all ugly and should be avoided at any cost. As always, best practice is to use the best tool for the job.</p>
<p>I mention this because I&#8217;ve noticed that <a href="http://lighthouseapp.com/">Lighthouse</a> has chosen to use <a href="http://beast.caboo.se/">Beast</a>, a sleek and relatively new Rails-based forum for their support. I&#8217;ve experimented with Beast, and I love it! The glaring problem I saw when evaluating Beast for our own use here at <a href="http://lunardawn.ca/">lunardawn</a> is that it doesn&#8217;t have *any* spam protection, as seen at the spam-filled <a href="http://forum.activereload.net/">Lighthouse support</a>. It wouldn&#8217;t take much at all to integrate with <a href="http://akismet.com/">Akismet</a> to block most spam, and admittedly I could have patched Beast as such pretty fast, but we want to use the best tool for the job while taking away as little development time from our core product as possible.</p>
<p>So for us, we&#8217;re looking at either <a href="http://www.phpbb.com/">phpBB</a>, which has a large community dedicated to anti-spam measures, or lussumo&#8217;s <a href="http://getvanilla.com/">Vanilla</a>, which seems to avoid spam at the moment solely based on its small market share (obviously not scalable to any degree).</p>
]]></content:encoded>
			<wfw:commentRss>http://archived.bradybouchard.ca/2008/07/using-rails-just-because/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>all puff, no moo</title>
		<link>http://archived.bradybouchard.ca/2008/03/all-puff-no-moo/</link>
		<comments>http://archived.bradybouchard.ca/2008/03/all-puff-no-moo/#comments</comments>
		<pubDate>Mon, 03 Mar 2008 22:58:27 +0000</pubDate>
		<dc:creator>brady</dc:creator>
				<category><![CDATA[dev and design]]></category>
		<category><![CDATA[reviews]]></category>
		<category><![CDATA[business cards]]></category>
		<category><![CDATA[minicards]]></category>
		<category><![CDATA[moo cards]]></category>

		<guid isPermaLink="false">http://blog.bradybouchard.ca/archives/4</guid>
		<description><![CDATA[I got my minicards today from moo, and for the sake of those interested in buying some of their own, I thought I would offer my quick first impressions. A lot smaller than I realized! About half the height of a normal business card. I looked at a ruler when I was ordering to get an [...]]]></description>
			<content:encoded><![CDATA[<p>I got my minicards today from <a href="http://moo.com/">moo</a>, and for the sake of those interested in buying some of their own, I thought I would offer my quick first impressions.</p>
<ul>
<li>A lot smaller than I realized! About half the height of a normal business card. I looked at a ruler when I was ordering to get an idea of the size and I knew they&#8217;d be small, but these are pretty tiny.</li>
<li>The tiny thing works for their purpose though, I think. Makes them more of a &#8220;quick-everyone-take-one-we-have-lots&#8221; sort of item. Better for trade shows and the like than for normal business &#8211; I definitely think sticking with the standard business card-size is better for individual client introductions.</li>
<li>Excellent, high-quality paper stock. I would guess about twice as thick as a regular business card. It feels good to the touch, which is (let&#8217;s face it) mostly what matters.</li>
<li>The printing (I got my company logo on the front) leaves a lot to be desired. The vibrant colours of our logo are very washed out. Looks like what happens to paper when it goes through the wash &#8211; bold, navy blues are converted to light, timid-looking cyans.</li>
<li>Same goes for text on the front. The text is part of the logo (as moo doesn&#8217;t allow text on the front), and you can tell. The dots from the colour inkjet cartridge that printed the text are clearly visible, and it gives it a fuzzy texture.</li>
<li>Text on the back is crisp, sharp, and most importantly, very black. Looks very good.</li>
</ul>
<p>Overall, I&#8217;m getting more of a &#8220;meh&#8221; reaction to the cards than I would have liked &#8211; I was hoping that these could be the little &#8220;wow&#8221; factor that I&#8217;m looking for during a first impression, but unfortunately I don&#8217;t think they&#8217;re up to snuff. Not bad cards if you stick to straight type though, and really good quality stock, though I think I&#8217;ll stick to regular business cards in the future.</p>
]]></content:encoded>
			<wfw:commentRss>http://archived.bradybouchard.ca/2008/03/all-puff-no-moo/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->