<?xml version="1.0" encoding="UTF-8"?><rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
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/"
> <channel><title>Comments on: 5 Favorite Excuses to Avoid Fixing Your Architecture</title> <atom:link href="http://hackerboss.com/5-favorite-techniques-to-avoid-fixing-your-architecture/feed/" rel="self" type="application/rss+xml" /><link>http://hackerboss.com/5-favorite-techniques-to-avoid-fixing-your-architecture/</link> <description>Developing software and managing development teams.</description> <lastBuildDate>Mon, 07 May 2012 11:50:39 +0000</lastBuildDate> <generator>http://wordpress.org/?v=</generator> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>By: Ville Laurikari</title><link>http://hackerboss.com/5-favorite-techniques-to-avoid-fixing-your-architecture/comment-page-1/#comment-1170</link> <dc:creator>Ville Laurikari</dc:creator> <pubDate>Tue, 13 Apr 2010 07:25:41 +0000</pubDate> <guid
isPermaLink="false">http://hackerboss.com/?p=1191#comment-1170</guid> <description>I agree that you should definitely not change your architecture (or worse, rewrite from scratch) for no reason.  Certainly I&#039;m not saying you should stop fixing bugs and introducing features.  In fact, there&#039;s almost never a good (business) reason to do that.But sometimes, although rarely, it&#039;s the architecture that is slowing down you compared to competition.  Note that I&#039;m using the term architecture here quite loosely.  Often it&#039;s possible to do an architectural update &quot;on the side&quot; without stopping all other work.Thanks for your comment and the links, they all make for really good reading.</description> <content:encoded><![CDATA[<p>I agree that you should definitely not change your architecture (or worse, rewrite from scratch) for no reason.  Certainly I&#8217;m not saying you should stop fixing bugs and introducing features.  In fact, there&#8217;s almost never a good (business) reason to do that.</p><p>But sometimes, although rarely, it&#8217;s the architecture that is slowing down you compared to competition.  Note that I&#8217;m using the term architecture here quite loosely.  Often it&#8217;s possible to do an architectural update &#8220;on the side&#8221; without stopping all other work.</p><p>Thanks for your comment and the links, they all make for really good reading.</p> ]]></content:encoded> </item> <item><title>By: Slobodan Blazeski</title><link>http://hackerboss.com/5-favorite-techniques-to-avoid-fixing-your-architecture/comment-page-1/#comment-1160</link> <dc:creator>Slobodan Blazeski</dc:creator> <pubDate>Mon, 12 Apr 2010 13:21:43 +0000</pubDate> <guid
isPermaLink="false">http://hackerboss.com/?p=1191#comment-1160</guid> <description>How about our system is online and facing serious competition. If we stop fixing bugs and introducing features and instead spend time on luxuries like fixing our architecture we&#039;ll be closing doors in less than a year. Then nobody will care how good our architecture is.http://www.laputan.org/mud/mud.html
http://www.jwz.org/doc/worse-is-better.html
http://www.inc.com/magazine/20091101/does-slow-growth-equal-slow-death.html</description> <content:encoded><![CDATA[<p>How about our system is online and facing serious competition. If we stop fixing bugs and introducing features and instead spend time on luxuries like fixing our architecture we&#8217;ll be closing doors in less than a year. Then nobody will care how good our architecture is.</p><p><a
href="http://www.laputan.org/mud/mud.html" rel="nofollow">http://www.laputan.org/mud/mud.html</a><br
/> <a
href="http://www.jwz.org/doc/worse-is-better.html" rel="nofollow">http://www.jwz.org/doc/worse-is-better.html</a><br
/> <a
href="http://www.inc.com/magazine/20091101/does-slow-growth-equal-slow-death.html" rel="nofollow">http://www.inc.com/magazine/20091101/does-slow-growth-equal-slow-death.html</a></p> ]]></content:encoded> </item> <item><title>By: hackerboss</title><link>http://hackerboss.com/5-favorite-techniques-to-avoid-fixing-your-architecture/comment-page-1/#comment-402</link> <dc:creator>hackerboss</dc:creator> <pubDate>Mon, 12 Oct 2009 20:06:15 +0000</pubDate> <guid
isPermaLink="false">http://hackerboss.com/?p=1191#comment-402</guid> <description>&lt;p&gt;5 Favorite Techniques to Avoid Fixing Your Architecture: &lt;a href=&quot;http://bit.ly/1hCzdI&quot; rel=&quot;nofollow&quot;&gt;http://bit.ly/1hCzdI&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;i&gt;This comment was originally posted on &lt;a href=&quot;http://twitter.com/hackerboss/statuses/4816139271&quot; rel=&quot;nofollow&quot;&gt;Twitter&lt;/a&gt;&lt;/i&gt;&lt;/p&gt;</description> <content:encoded><![CDATA[<p>5 Favorite Techniques to Avoid Fixing Your Architecture: <a
href="http://bit.ly/1hCzdI" rel="nofollow">http://bit.ly/1hCzdI</a></p><p><i>This comment was originally posted on <a
href="http://twitter.com/hackerboss/statuses/4816139271" rel="nofollow">Twitter</a></i></p> ]]></content:encoded> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (enhanced) (user agent is rejected)
Database Caching using disk

Served from: hackerboss.com @ 2012-05-19 03:57:56 -->
