<?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: My Bookshelf</title>
	<atom:link href="http://www.mcdonaldland.info/2008/04/04/my-bookshelf/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mcdonaldland.info/2008/04/04/my-bookshelf/</link>
	<description>A magical discussion of software, economics, and other assorted theories. but mainly software.</description>
	<lastBuildDate>Tue, 31 Jan 2012 22:21:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Jason McDonald</title>
		<link>http://www.mcdonaldland.info/2008/04/04/my-bookshelf/#comment-390</link>
		<dc:creator>Jason McDonald</dc:creator>
		<pubDate>Mon, 14 Apr 2008 12:52:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.mcdonaldland.info/2008/04/04/my-bookshelf/#comment-390</guid>
		<description>I&#039;m only about a 3rd through it right now - big book -  but it has a lot of good information in it. The amount you take away from it will depend on the point you are in your career. If you are just starting out you&#039;ll find tons of useful information. If you have been in the field for a while you&#039;ll still find tons of useful information, only you would typically know a greater portion of it already.

For example, one of the things discussed is the differences, pros, and cons between top down design and bottom up design. If you have done a fair amount of real world architecture already then this is bound to be a lesson already learned. However, if you have little architecture exposure then this is an invaluable lesson.

In a sentence, it is a good book (seminal perhaps) and worth the read.</description>
		<content:encoded><![CDATA[<p>I&#8217;m only about a 3rd through it right now &#8211; big book &#8211;  but it has a lot of good information in it. The amount you take away from it will depend on the point you are in your career. If you are just starting out you&#8217;ll find tons of useful information. If you have been in the field for a while you&#8217;ll still find tons of useful information, only you would typically know a greater portion of it already.</p>
<p>For example, one of the things discussed is the differences, pros, and cons between top down design and bottom up design. If you have done a fair amount of real world architecture already then this is bound to be a lesson already learned. However, if you have little architecture exposure then this is an invaluable lesson.</p>
<p>In a sentence, it is a good book (seminal perhaps) and worth the read.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cohem</title>
		<link>http://www.mcdonaldland.info/2008/04/04/my-bookshelf/#comment-389</link>
		<dc:creator>cohem</dc:creator>
		<pubDate>Mon, 14 Apr 2008 12:32:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.mcdonaldland.info/2008/04/04/my-bookshelf/#comment-389</guid>
		<description>&lt;b&gt;Code Complete: A Practical Handbook of Software Construction&lt;/b&gt;

What do you think of this book?</description>
		<content:encoded><![CDATA[<p><b>Code Complete: A Practical Handbook of Software Construction</b></p>
<p>What do you think of this book?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

