<?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: How to code better: new book from ThoughtWorks</title>
	<atom:link href="http://www.itwriting.com/blog/586-how-to-code-better-new-book-from-thoughtworks.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.itwriting.com/blog/586-how-to-code-better-new-book-from-thoughtworks.html</link>
	<description>Tech writing blog</description>
	<lastBuildDate>Sun, 12 Feb 2012 21:04:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Michael Robinson</title>
		<link>http://www.itwriting.com/blog/586-how-to-code-better-new-book-from-thoughtworks.html/comment-page-1#comment-90663</link>
		<dc:creator>Michael Robinson</dc:creator>
		<pubDate>Thu, 24 Apr 2008 19:20:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.itwriting.com/blog/?p=586#comment-90663</guid>
		<description>Some people need hard and fast rules to follow.  They see the world as black and white, and they need solid direction from a perceived source of authority.  Many developers are like that.  Innovative, creative developers who can make their own competent judgement calls about design are frankly a rarity.  And I&#039;d rather have a developer following a set of rules, even if they are somewhat restrictive, than a developer writing continuous streams of unmaintainable uncommented garbage code.  In any case, any methodology can only be a guideline, an approach that we attempt to adhere to as best we can while meeting the needs of our clients.  Only in research or example projects can architectures be developed that perfectly fit any non-trivial methodology.  The real world is always more complex and exception-ridden than the products of such methodologies: ideal structures that appeal to us aesthetically, or readily lend themselves to maintainability.</description>
		<content:encoded><![CDATA[<p>Some people need hard and fast rules to follow.  They see the world as black and white, and they need solid direction from a perceived source of authority.  Many developers are like that.  Innovative, creative developers who can make their own competent judgement calls about design are frankly a rarity.  And I&#8217;d rather have a developer following a set of rules, even if they are somewhat restrictive, than a developer writing continuous streams of unmaintainable uncommented garbage code.  In any case, any methodology can only be a guideline, an approach that we attempt to adhere to as best we can while meeting the needs of our clients.  Only in research or example projects can architectures be developed that perfectly fit any non-trivial methodology.  The real world is always more complex and exception-ridden than the products of such methodologies: ideal structures that appeal to us aesthetically, or readily lend themselves to maintainability.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Allen</title>
		<link>http://www.itwriting.com/blog/586-how-to-code-better-new-book-from-thoughtworks.html/comment-page-1#comment-89807</link>
		<dc:creator>Jonathan Allen</dc:creator>
		<pubDate>Mon, 21 Apr 2008 19:58:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.itwriting.com/blog/?p=586#comment-89807</guid>
		<description>Oh no, another book on dogmatic advice that is sure to lead to another generation programmers obsessing over inane ideas.</description>
		<content:encoded><![CDATA[<p>Oh no, another book on dogmatic advice that is sure to lead to another generation programmers obsessing over inane ideas.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

