<?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: Reading Up: Books Every Programmer Should Read</title>
	<atom:link href="http://www.lagerweij.com/2010/08/31/reading-up-books-every-programmer-should-read/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lagerweij.com/2010/08/31/reading-up-books-every-programmer-should-read/</link>
	<description>Wouter Lagerweij</description>
	<lastBuildDate>Thu, 16 Feb 2012 06:03:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Draško Gomboc (@draskogomboc)</title>
		<link>http://www.lagerweij.com/2010/08/31/reading-up-books-every-programmer-should-read/comment-page-1/#comment-3512</link>
		<dc:creator>Draško Gomboc (@draskogomboc)</dc:creator>
		<pubDate>Wed, 01 Feb 2012 21:21:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.lagerweij.com/?p=59#comment-3512</guid>
		<description>Literatura - http://t.co/9W8VBO1r</description>
		<content:encoded><![CDATA[<p>Literatura &#8211; <a href="http://t.co/9W8VBO1r" rel="nofollow">http://t.co/9W8VBO1r</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Line by Line &#187; Technical Excellence: Why you should TDD!</title>
		<link>http://www.lagerweij.com/2010/08/31/reading-up-books-every-programmer-should-read/comment-page-1/#comment-3252</link>
		<dc:creator>Line by Line &#187; Technical Excellence: Why you should TDD!</dc:creator>
		<pubDate>Fri, 27 Jan 2012 00:22:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.lagerweij.com/?p=59#comment-3252</guid>
		<description>[...] a developer, it&#8217;s important to keep learning. There a lot of great books out there. And new ones coming out all the time. But don&#8217;t just read. Practice. At Qualogy I&#8217;ve [...]</description>
		<content:encoded><![CDATA[<p>[...] a developer, it&#8217;s important to keep learning. There a lot of great books out there. And new ones coming out all the time. But don&#8217;t just read. Practice. At Qualogy I&#8217;ve [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Line by Line &#187; Reading up: 5 Books To Read If You Want To Really Understand Agile</title>
		<link>http://www.lagerweij.com/2010/08/31/reading-up-books-every-programmer-should-read/comment-page-1/#comment-1005</link>
		<dc:creator>Line by Line &#187; Reading up: 5 Books To Read If You Want To Really Understand Agile</dc:creator>
		<pubDate>Wed, 03 Aug 2011 21:06:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.lagerweij.com/?p=59#comment-1005</guid>
		<description>[...] year, I posted an overview of some books every programmer should read. Those still stand, and I find more and more examples where I would like to re-iterate the advice [...]</description>
		<content:encoded><![CDATA[<p>[...] year, I posted an overview of some books every programmer should read. Those still stand, and I find more and more examples where I would like to re-iterate the advice [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Line by Line &#187; Code Cleaning: A Refactoring Example In 50 Easy Steps</title>
		<link>http://www.lagerweij.com/2010/08/31/reading-up-books-every-programmer-should-read/comment-page-1/#comment-708</link>
		<dc:creator>Line by Line &#187; Code Cleaning: A Refactoring Example In 50 Easy Steps</dc:creator>
		<pubDate>Sun, 29 May 2011 00:37:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.lagerweij.com/?p=59#comment-708</guid>
		<description>[...] found the code in that state, and simply didn&#8217;t know where to start to improve things. Some programmers may not even have read Clean Code, Refactoring, or the Pragmatic Programmer! And maybe no one ever told them they [...]</description>
		<content:encoded><![CDATA[<p>[...] found the code in that state, and simply didn&#8217;t know where to start to improve things. Some programmers may not even have read Clean Code, Refactoring, or the Pragmatic Programmer! And maybe no one ever told them they [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hypertech Power Programmer 3 for GM</title>
		<link>http://www.lagerweij.com/2010/08/31/reading-up-books-every-programmer-should-read/comment-page-1/#comment-89</link>
		<dc:creator>Hypertech Power Programmer 3 for GM</dc:creator>
		<pubDate>Wed, 01 Sep 2010 01:49:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.lagerweij.com/?p=59#comment-89</guid>
		<description>[...] Line by Line &#187; Reading Up: Books Every Programmer Should Read [...]</description>
		<content:encoded><![CDATA[<p>[...] Line by Line &raquo; Reading Up: Books Every Programmer Should Read [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://www.lagerweij.com/2010/08/31/reading-up-books-every-programmer-should-read/comment-page-1/#comment-88</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Tue, 31 Aug 2010 16:22:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.lagerweij.com/?p=59#comment-88</guid>
		<description>wouter, thanks for the list.  I have to second clean code.  Clean code taught me how to write a clear function.  Clean code also helped me see that writing good code is like writing a good sentence.  I would also like to recommend Pragmatic Programer (http://www.amazon.com/dp/020161622X?ref=servicebrook-20).  The Pragmatic Programer really helped me see that there was so much more to programming than writing code.</description>
		<content:encoded><![CDATA[<p>wouter, thanks for the list.  I have to second clean code.  Clean code taught me how to write a clear function.  Clean code also helped me see that writing good code is like writing a good sentence.  I would also like to recommend Pragmatic Programer (<a href="http://www.amazon.com/dp/020161622X?ref=servicebrook-20" rel="nofollow">http://www.amazon.com/dp/020161622X?ref=servicebrook-20</a>).  The Pragmatic Programer really helped me see that there was so much more to programming than writing code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Grayson</title>
		<link>http://www.lagerweij.com/2010/08/31/reading-up-books-every-programmer-should-read/comment-page-1/#comment-87</link>
		<dc:creator>Grayson</dc:creator>
		<pubDate>Tue, 31 Aug 2010 15:42:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.lagerweij.com/?p=59#comment-87</guid>
		<description>Really surprised not to see The Pragmatic Programmer. My hands down absolute favorite is Ship It!: A Practical Guide to Successful Software Projects.

http://pragprog.com/titles/tpp/the-pragmatic-programmer
http://pragprog.com/titles/prj/ship-it</description>
		<content:encoded><![CDATA[<p>Really surprised not to see The Pragmatic Programmer. My hands down absolute favorite is Ship It!: A Practical Guide to Successful Software Projects.</p>
<p><a href="http://pragprog.com/titles/tpp/the-pragmatic-programmer" rel="nofollow">http://pragprog.com/titles/tpp/the-pragmatic-programmer</a><br />
<a href="http://pragprog.com/titles/prj/ship-it" rel="nofollow">http://pragprog.com/titles/prj/ship-it</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wouter Lagerweij&#8217;s Blog: Reading Up: Books Every Programmer Should Read &#124; Development Blog With Code Updates : Developercast.com</title>
		<link>http://www.lagerweij.com/2010/08/31/reading-up-books-every-programmer-should-read/comment-page-1/#comment-86</link>
		<dc:creator>Wouter Lagerweij&#8217;s Blog: Reading Up: Books Every Programmer Should Read &#124; Development Blog With Code Updates : Developercast.com</dc:creator>
		<pubDate>Tue, 31 Aug 2010 13:49:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.lagerweij.com/?p=59#comment-86</guid>
		<description>[...] Lagerweij has posted a list of books he thinks every programmer should read to help them get a better handle on their process overall (they apply to any language out there, [...]</description>
		<content:encoded><![CDATA[<p>[...] Lagerweij has posted a list of books he thinks every programmer should read to help them get a better handle on their process overall (they apply to any language out there, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reading Up: Books Every Programmer Should Read</title>
		<link>http://www.lagerweij.com/2010/08/31/reading-up-books-every-programmer-should-read/comment-page-1/#comment-85</link>
		<dc:creator>Reading Up: Books Every Programmer Should Read</dc:creator>
		<pubDate>Tue, 31 Aug 2010 13:47:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.lagerweij.com/?p=59#comment-85</guid>
		<description>[...] via Line by Line » Read­ing Up: Books Every Pro­gram­mer Should Read. [...]</description>
		<content:encoded><![CDATA[<p>[...] via Line by Line » Read­ing Up: Books Every Pro­gram­mer Should Read. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wouter</title>
		<link>http://www.lagerweij.com/2010/08/31/reading-up-books-every-programmer-should-read/comment-page-1/#comment-84</link>
		<dc:creator>wouter</dc:creator>
		<pubDate>Tue, 31 Aug 2010 13:34:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.lagerweij.com/?p=59#comment-84</guid>
		<description>Thanks for the tip! I&#039;ve been reading some of his articles on IBM developerworks (on TDD and emergent design) and those have been excellent.</description>
		<content:encoded><![CDATA[<p>Thanks for the tip! I&#8217;ve been reading some of his articles on IBM developerworks (on TDD and emergent design) and those have been excellent.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Served from: www.lagerweij.com @ 2012-02-23 03:04:54 by W3 Total Cache -->
