    <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  :: Editorial</title>
        <link>https://members.accu.org/index.php/articles/511</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">Journal Editorial + Overload Journal #34 - Oct 1999</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/c185/">Editorial</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/c78/">Overload</a>

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

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

                    -                        <a href="https://members.accu.org/index.php/articles/c185+170/">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;Editorial</h1>
<p><strong>Author:</strong>&nbsp;</p>
<p>
<strong>Date:</strong> 26 October 1999 17:50:54 +01:00 or Tue, 26 October 1999 17:50:54 +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>Advice for
authors:</h2>
</div>
<div class="sect2" lang="en">
<div class="titlepage">
<h3><a name="d0e21" id="d0e21"></a>#1 Introduce the
topic.</h3>
</div>
<p>In previous years this magazine has keenly covered the progress
of the C++ Standard through the ISO standardisation process.</p>
</div>
<div class="sect2" lang="en">
<div class="titlepage">
<h3><a name="d0e26" id="d0e26"></a>#2 Provide some
background material</h3>
</div>
<p>The International Standards Organisation (http://www.iso.ch/) is
somewhat bureaucratic in nature, as its members are mostly national
standards bodies, themselves paid for by their sponsoring
governments. Thus ISO's structure and behaviour tends to be
governmental.</p>
<p>I attended a couple of national standards body meetings, at BSI,
but was never fortunate enough to attend a real convening of the
ISO Working Group. Each national body sends a delegation of
industry experts to discuss the work in progress and to tender
their national vote on contentious issues.</p>
<p>The C++ Working Group would meet concurrently with the American
national body meeting, ANSI, since the majority of attendees
participated in both. Some members could be representing their
country in the ISO meeting, and their company or their own personal
interests in the ANSI meeting. Thus an individual might vote
differently on an issue depending on which hat they'd be wearing at
the time.</p>
</div>
<div class="sect2" lang="en">
<div class="titlepage">
<h3><a name="d0e35" id="d0e35"></a>#3 Write about
what you know.</h3>
</div>
<p>In contrast, over the past couple of years, I have been
attending the meetings of the Internet Engineering Task Force
(IETF). The Internet has no government, but without standards it
could never have been created, or continue to evolve.</p>
<p>The IETF meets three times a year - always in unglamorous
locations - to deter the junketeers. Two thousand engineers descend
upon some provincial capital to consume the local beer and clog the
local ISPs with traffic.</p>
<p>The corridors of the conference hotel are littered with isolated
nests of laptop users. All crouching on the floor, in their fading
free t-shirts, silently hacking away next to each other. They
congregate not to talk, but to overload the power sockets hidden
behind the ornamental vegetation. They don't talk because they're
plugged into their own online virtual community. A wireless LAN is
installed throughout the building, and every laptop gets a wireless
modem. The engineering discussions occur in the physical and
virtual plains simultaneously.</p>
<p>The IETF seems to have been organised as a somewhat unique
social experiment. To attend is to be a member, and every member
has equal voting rights. Members represent only themselves, with
flouting of employer or national affiliations being frowned upon.
The Internet and the IETF have a symbiotic relationship explaining
why they are both as democratising as each other.</p>
<p>There have to be checks and balances in every organisation, but
beyond these the IETF has very few rules and regulations. The work
is broken down into perhaps a hundred Working Groups. There are no
closed sessions - all Working Group activities are advertised and
open to all.</p>
<p>The Internet Grey Beards, those who hark from the beginning of
internet time, hover at the back of the working group meetings
offering up their ancient wisdom to prevent groups from
floundering, or falling down rat holes never to return.</p>
<p>The Working Groups meet to discuss and resolve issues, but there
is no voting mechanism. Work always has to progress by general
consensus, as in the ISO Working Groups, but when it comes down to
a vote, there is no formal vote. Each Working Group Chair has their
own technique, but the usual litmus test applied is the raising of
hands, or more amusingly the loudness of humming. Humming is an
analogue test, as a few loud hummers is equivalent to many quiet
hummers, so the hummer can express the depth of their agreement
with the strength of their hum.</p>
</div>
<div class="sect2" lang="en">
<div class="titlepage">
<h3><a name="d0e52" id="d0e52"></a>#4 Repeat your
introduction as a conclusion</h3>
</div>
<p>Damn, my introduction doesn't work as a conclusion.</p>
</div>
<div class="sect2 titlepage" lang="en">
<h3><a name="d0e57" id="d0e57"></a>#0 Start with an
essay plan.</h3>
</div>
</div>
</p>
<p><strong>Notes:</strong>&nbsp;</p>
<p><em>More fields may be available via dynamicdata ..</em></p>
</div>
</channel>
</rss>
