    <rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/">
     <channel>
        <title>ACCU  :: A Perspective on Two Books</title>
        <link>https://members.accu.org/index.php/journals/1019</link>
        <description>Professionalism in Programming</description>
        <dc:language>en-us</dc:language> 
        <dc:creator>Administrator</dc:creator> 
        <admin:generatorAgent rdf:resource="http://www.xaraya.org" /> 
        <admin:errorReportsTo rdf:resource="mailto:webeditor@accu.org" />
       <sy:updatePeriod>hourly</sy:updatePeriod>
       <sy:updateFrequency>1</sy:updateFrequency>
       <docs>http://backend.userland.com/rss</docs>


        <h2>Journal Articles</h2>


<div class="xar-mod-head"><span class="xar-mod-title">CVu Journal Vol 12, #4 - Jul 2000</span></div>

<table border="0" cellpadding="1" cellspacing="0">
    <tbody>
    <tr>
        <td valign="top">
            Browse in :
       </td>
       <td valign="top">

                                            <a href="https://members.accu.org/index.php/journals/">All</a>

                     &gt;                         <a href="https://members.accu.org/index.php/journals/c76/">Journals</a>

                     &gt;                         <a href="https://members.accu.org/index.php/journals/c77/">CVu</a>

                     &gt;                         <a href="https://members.accu.org/index.php/journals/c125/">124</a>
                    (22)
<br />
</td>
   </tr>
   </tbody>
</table>




<div class="xar-error">
   <p>
 <strong>Note:</strong> when you create a new publication type,
the articles module will automatically use the templates
<em>user-display-[publicationtype].xt</em>
and <em>user-summary-[publicationtype].xt</em>.
If those templates do not exist when you try to preview or display a new article,
you'll get this warning :-)  Please place your own templates in themes/<em>yourtheme</em>/modules/articles . The templates will get the extension .xt there. </p>
</div>
<div class="xar-norm xar-standard-box-padding">
   <h1><strong>Title:</strong>&nbsp;A Perspective on Two Books</h1>
<p><strong>Author:</strong>&nbsp;</p>
<p>
<strong>Date:</strong> 03 July 2000 13:15:37 +01:00 or Mon, 03 July 2000 13:15:37 +01:00</p>
<p><strong>Summary:</strong>&nbsp;</p>
<p><strong>Body:</strong>&nbsp;<div class="sect1" lang="en">
<div class="titlepage">
<h2><a name="d0e18" id="d0e18"></a></h2>
</div>
<p>You recently published reviews of Kernighan and Pike's,
<i class="citetitle">The Practice of Programming</i> and Hunt and
Thomas's, <i class="citetitle">The Pragmatic Programmer</i>.</p>
<p>On the strength of your comments, I bought both books, which I
have read.</p>
<p>Now, it is not that I disagree fundamentally with your
enthusiasm for these titles. Rather I would just like to point out
to intending readers the disparity of the approaches taken.</p>
<p>Like yourself I was greatly impressed with K &amp; P, so much so
that I immediately bought their The Unix Programming Environment
and I was not disappointed by that either. Both these are full of
practical, useful, meaty, hands-on tips. Whole chunks of code can
be lifted from the text and applied immediately. My eyes were
opened. Some of the material might be a bit dated (preference for
shell scripts rather than Perl, troff rather than TEX), but such is
the nature of Unix that tools are no less effective for their age!
It is the philosophy that matters, not the particulars. Agreed,
these are super, perhaps classical reads.</p>
<p>But the H &amp; T books is another matter. It is comparatively
woolly. 120 pages pass before one encounters a piece of code that
can actually be put to practical use. Ironically H &amp; T often
give the same advice as K &amp; P: use make, automate testing
procedures, choose a good ascii-type, programmable editor ... But
it is done at a distance - the examples are not concrete, they are
not hands on. I left this book feeling: &quot;interesting read, but
lacks depth, lacks conciseness&quot;. It talks about being practical,
rather than being itself practical. Humorous idioms like: &quot;Use
Tracer Bullets&quot;, or &quot;The Cat Ate My Source Code&quot; help to carry
subtle points. But there are occasional clangers: &quot;By architecting
your system ...&quot; !</p>
<p>Woolly as it might be, it offers some good advice on keeping the
specification process under control, joining professional societies
and reading material. A lot of the listed urls are dead.</p>
<p>Interestingly both these books miss a tip that I think should be
considered by all programmers and it is easily implemented: learn
how to touch type. (It cost me 30 quid to learn 20 years ago and it
has proved to be the best money ever I spent - helps me greatly
when writing book reviews.)</p>
<p>But essentially your enthusiasm is well founded. Both books have
something valuable to say, although from different
perspectives.</p>
</div>
</p>
<p><strong>Notes:</strong>&nbsp;</p>
<p><em>More fields may be available via dynamicdata ..</em></p>
</div>
</channel>
</rss>
