    <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  :: The Wall</title>
        <link>https://members.accu.org/index.php/articles/1076</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>




<div class="xar-mod-head"><span class="xar-mod-title">Letters to the Editor + CVu Journal Vol 12, #6 - Dec 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/articles/">All</a>

                     &gt;                         <a href="https://members.accu.org/index.php/articles/c184/">Journal Columns</a>

                     &gt;                         <a href="https://members.accu.org/index.php/articles/c186/">LettersEditor</a>
<br />

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

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

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

                     &gt;                         <a href="https://members.accu.org/index.php/articles/c123/">126</a>
<br />

                                            <a href="https://members.accu.org/index.php/articles/c186-123/">Any of these categories</a>

                    -                        <a href="https://members.accu.org/index.php/articles/c186+123/">All of these categories</a>
<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;The Wall</h1>
<p><strong>Author:</strong>&nbsp;</p>
<p>
<strong>Date:</strong> 08 December 2000 13:15:41 +00:00 or Fri, 08 December 2000 13:15:41 +00:00</p>
<p><strong>Summary:</strong>&nbsp;</p>
<p><strong>Body:</strong>&nbsp;<div class="sect1" lang="en">
<div class="titlepage">
<h2><a name="d0e20" id="d0e20"></a>On Book
Reviewing</h2>
</div>
<p>Dear Francis,</p>
<p>In the last C Vu that I read, someone raised a discussion point
about the book reviews, that a lot of the reviewers are not able to
review the technical quality of the book. Some suggestions were
made which could improve things.</p>
<p>A while ago, I once suggested that reviewers could give an
update after a year, whether the book would still be technically
relevant. What would be possible to achieve, without putting too
much of a burden on the web site maintainers?</p>
<p>I recently noticed again, in a book some technically incorrect
APIs. I did not notice this when I was reading the book for review,
but only when I started using the book.</p>
<p>Also, may be we could add a little table to the book reviews,
e.g. stating about the reviewers back ground, number of typing
mistakes, pleasing layout, good index, target audience. You do not
always mention those in a review, but it would make the reviews
slightly more elaborate. For example, I never state recommended or
not recommended with my reviews. Probably my fault, but my reviews
have not always been correctly interpreted, I did not always agree
with the rating someone made up out of my review.</p>
<p>Silvia de Beer</p>
<p class="c3"><span class="remark">If a reviewer disagrees with a
classification they should let Peter Hamilton know, I guess that
<tt class="email">&lt;<a href=
"mailto:webmaster@accu.org">webmaster@accu.org</a>&gt;</tt> should
reach him. If reviewers want to add to, or change a review in the
light of experience, I would be very happy to have these changes
sent direct to me. They should include details of the issue in
which the review originally appeared as well as the title of the
book.</span></p>
<p class="c3"><span class="remark">Similarly, if others want to add
detail or caveats to a published review without writing a
completely new review (which they should do if the substantially
disagree with the original) they can send them to me together with
the same details (issue number and book title).</span></p>
</div>
</p>
<p><strong>Notes:</strong>&nbsp;</p>
<p><em>More fields may be available via dynamicdata ..</em></p>
</div>
</channel>
</rss>
