<?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>Center for REALTOR® Technology Web Log &#187; Books</title>
	<atom:link href="http://blog.realtors.org/crt/category/books/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.realtors.org/crt</link>
	<description>CRT's communications</description>
	<lastBuildDate>Wed, 17 Mar 2010 14:00:20 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Are you a pragmatic programmer?</title>
		<link>http://blog.realtors.org/crt/2006/03/30/are-you-a-pragmatic-programmer/</link>
		<comments>http://blog.realtors.org/crt/2006/03/30/are-you-a-pragmatic-programmer/#comments</comments>
		<pubDate>Thu, 30 Mar 2006 18:45:25 +0000</pubDate>
		<dc:creator>Keith Garner</dc:creator>
				<category><![CDATA[Books]]></category>

		<guid isPermaLink="false">http://blog.realtors.org/crt/2006/03/30/are-you-a-pragmatic-programmer/</guid>
		<description><![CDATA[In the 90s, when I was in the process of learning Unix  as well as learning to be a better programmer, you couldn&#8217;t go wrong with any title published by O&#8217;Reilly.&#160; There were a smaller organization than they are now and almost everything I read by them was a great source of knowledge.&#160; If [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://blog.realtors.org/crt/wp-content/uploads/2006/03/books.gif" alt="books.gif" width="120" height="81" align="right" />In the 90s, when I was in the process of learning <a href="http://en.wikipedia.org/wiki/Unix">Unix</a>  as well as learning to be a better programmer, you couldn&#8217;t go wrong with any title published by <a href="http://www.oreilly.com/">O&#8217;Reilly</a>.&nbsp; There were a smaller organization than they are now and almost everything I read by them was a great source of knowledge.&nbsp; If a book by them was on a topic I was interested in, I would just buy it without reading any reviews or thumbing through it.&nbsp; As they&#8217;ve gotten bigger I&#8217;ve found that not every title is up to the quality I associated with the name O&#8217;Reilly.&nbsp; Not to say they still don&#8217;t have <a href="http://www.oreilly.com/catalog/dns4/">some</a>  <a href="http://www.oreilly.com/catalog/upt3/">excellent</a>  <a href="http://www.oreilly.com/catalog/javanut5/">books</a>  I still turn too.&nbsp; (I&#8217;d still turn to the <a href="http://www.oreilly.com/catalog/perlcdbs4/">perl books</a>  if I haven&#8217;t given up <a href="http://www.perl.org/">perl</a>  for health and sanity reasons.)</p>
<p>Lately, I&#8217;ve been reading books from another publishing house that reminds me of O&#8217;Reilly of old: <a href="http://www.pragmaticprogrammer.com/">The Pragmatic Programmers</a>.&nbsp; In fact, they are now the new wearers of the &quot;instant buy&quot; crown.</p>
<p>I read their first book, <a href="http://www.pragmaticprogrammer.com/ppbook/index.shtml">The Pragmatic Programmer: From Journeyman to Master</a>, in late 2000 and it was an eye opener for me, especially for such a small book.&nbsp; It validated many practices and &quot;rules&quot; I already followed without being explicitly introduced to them, and gave me a few more I should have been following.&nbsp; It instantly become one of my favorite books on programming and one that I often loan out or recommend.</p>
<p><span id="more-118"></span> My next experience with one of their books was last year when we started our conversion from <a href="http://www.nongnu.org/cvs/">CVS</a>  to <a href="http://subversion.tigris.org/">Subversion</a>.&nbsp; I picked up <a href="http://www.pragmaticprogrammer.com/titles/svn/index.html">Pragmatic Version Control: Using Subversion</a>  as a quick primer on the administration side of subversion as well as to help look at ways we can do source control better.&nbsp; It helped us through the initial transition and gave us a few ideas of things we should be doing in the future.&nbsp; For example, based on a suggestion in PVC, for libRETS&#8217;s dependencies, we now have checked in <a href="http://code.crt.realtors.org/projects/librets/browser/vendorsrc/">versions of the source</a>  as well as <a href="http://code.crt.realtors.org/projects/librets/browser/vendor/windows/">precompiled binaries</a>  to aid in building on Windows.</p>
<p>What really gave the pragmatic folks the crown was <a href="http://www.pragmaticprogrammer.com/titles/ruby/index.html">Programming Ruby: The Pragmatic Programmer&#8217;s Guide</a>.&nbsp; While I admit that I was eager to learn <a href="http://www.ruby-lang.org/">ruby</a>, I don&#8217;t think I would have absorbed it fast without this book.&nbsp; This is one of maybe three programming books I&#8217;ve read all the way through.&nbsp; The examples were straight forward and the writing kept it interesting.&nbsp; I&#8217;ve loaned this book out twice so far to others who have similarly good things to say.&nbsp; Dave Dribin remarked once that he kept trying to learn Python and that Python didn&#8217;t gel with him partially due to a lack of a good book.&nbsp; He&#8217;s a big Ruby proponent now as well.</p>
<p>I&#8217;ve got <a href="http://www.pragmaticprogrammer.com/titles/rails/index.html">Agile Web Development with Rails: A Pragmatic Guide</a> sitting on my shelf waiting to be read.&nbsp; Unfortunately, I haven&#8217;t had time to dig into it yet.&nbsp; Dave&#8217;s given it a thumbs up, so I&#8217;m sure it will be good.&nbsp; I guess I need to invent a good web project to give myself some need.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.realtors.org/crt/2006/03/30/are-you-a-pragmatic-programmer/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
