<?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>Yan Pritzker &#187; bugtracking</title>
	<atom:link href="http://yanpritzker.com/category/bugtracking/feed/" rel="self" type="application/rss+xml" />
	<link>http://yanpritzker.com</link>
	<description>photographer, entrepreneur, software engineer, musician, skier</description>
	<lastBuildDate>Thu, 26 Apr 2012 18:11:34 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<atom:link rel="next" href="http://yanpritzker.com/category/bugtracking/feed/?page=2" />

		<item>
		<title>Rails moves to Lighthouse</title>
		<link>http://yanpritzker.com/2008/04/16/rails-moves-to-lighthouse/</link>
		<comments>http://yanpritzker.com/2008/04/16/rails-moves-to-lighthouse/#comments</comments>
		<pubDate>Wed, 16 Apr 2008 16:39:26 +0000</pubDate>
		<dc:creator>yan</dc:creator>
				<category><![CDATA[bugtracking]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[rails]]></category>
		<category><![CDATA[thoughts]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://skwpspace.com/2008/04/16/rails-moves-to-lighthouse/</guid>
		<description><![CDATA[In a series of dev infrastructure changes, the Rails team is moving to Lighthouse as its bugtracking system. I wrote about Lighthouse more than a year ago as an application to watch in the bugtracking space, and now they&#8217;re coming into the limelight with official support from the Rails team. I&#8217;m really happy to see [...]]]></description>
			<content:encoded><![CDATA[<p>In a series of dev infrastructure changes, the <a href="http://weblog.rubyonrails.com/2008/4/15/rails-and-family-on-lighthouse">Rails team is moving to Lighthouse as its bugtracking system.</a> I <a href="http://skwpspace.com/2007/04/02/ui-matters/">wrote about Lighthouse</a> more than a year ago as an application to watch in the bugtracking space, and now they&#8217;re coming into the limelight with official support from the Rails team. </p>
<p>I&#8217;m really happy to see that the Rails team and 37 Signals are making this move because it will force Lighthouse to become an even better application as it meets demands of many projects that are sure to follow Rails. </p>
<p>Too many teams put up with products that have terrible usability like Bugzilla because many programmers tend not to think about usability as an important factor. We are used to command line interfaces and white text on black backgrounds. But believe it or not, using something like <a href="http://lighthouseapp.com/">Lighthouse</a> over say, Bugzilla, boosts your productivity because it is well designed and lets you get to the information you need more quickly and with less frustration. That said, <a href="http://trac.edgewall.org/">Trac</a> is still many levels above Bugzilla in usability and design so if you&#8217;re using an in-house product, I don&#8217;t know of many better ones.</p>
<div class="plus-one-wrap"><g:plusone href="http://yanpritzker.com/2008/04/16/rails-moves-to-lighthouse/"></g:plusone></div>]]></content:encoded>
			<wfw:commentRss>http://yanpritzker.com/2008/04/16/rails-moves-to-lighthouse/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

