    <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  :: From The Silicon Valley</title>
        <link>https://members.accu.org/index.php/articles/1022</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">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/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/c125/">124</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;From The Silicon Valley</h1>
<p><strong>Author:</strong>&nbsp;</p>
<p>
<strong>Date:</strong> 05 July 2000 13:15:38 +01:00 or Wed, 05 July 2000 13:15:38 +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 class="c2"><span class="remark">The following is reprinted from
the June issue of ACC++ent. ACC++ent is aimed at programmers and
developers in the Silicon Valley. It is at the initiative of the US
Executive Committee that manages those aspects of ACCU specific to
the North American Continent. Members include John Merrells (well
known to readers of Overload), Heather Standring who was a ACCU
Committee member in the days before she went to the USA and Reg
Charney who is, I think, the very first of our US members.
FG</span></p>
</div>
<div class="sect1" lang="en">
<div class="titlepage">
<h2><a name="d0e23" id="d0e23"></a>Editorial</h2>
</div>
<div class="sect2" lang="en">
<div class="titlepage">
<h3><a name="d0e26" id="d0e26"></a>Loyalty</h3>
</div>
<p>Loyalty is a constant refrain in the give and take of hiring and
being hired. No one admits to believing in it, but when push comes
to shove, it is expected. The chance to belong is a very real
motivator for most people. Thus, I was surprised recently by a
contract I saw. It outlines the operating conditions for
contractors working at a company with a terrific reputation. It
clearly separates those working at the company into two groups:
employees and contractors. As expected, employees get all the
benefits of employment. What is surprising was the effort made to
differentiate the non-employees. It extends from trivial matters to
gross strategic mistakes.</p>
<p>First, let me point out that both direct and temporary hires
work on the same projects and usually put in comparable hours. For
all intents and purposes, their work load is similar and how their
performance is judged is the same. The standards seem fair and
consistent for both.</p>
<p>However, a two-tier system exists. As a trivial example,
temporary employees are not allowed to use the recreational
facilities. At a serious strategic level, temporary workers are not
considered part of the team and are not allowed to participate in
team meetings, even though they may be the lead players or majority
of the teams! This makes the concept of a team a hollow parody and
destroys the intent of team building which is loyalty - that which
carries us together through good times and bad, and smoothes rough
waters.</p>
<p>I have no problem with differentiating between direct and
temporary workers based on pay versus benefits. That is a choice
for individuals to make. But to differentiate team members on the
basis of their hiring status is self-defeating to both parties.
There is no incentive to give that extra 10% on the part of the
temporary worker and the company can expect no loyalty or shared
vision when it needs it.</p>
<p>I recognise that tax and employment laws make life more
complicated, but it seems that we have allowed non-essential
factors to destroy mutually beneficial goals. As a lawyer friend of
mine once said, &quot;<span class="quote">Never let a lawyer make your
business decisions for you.</span>&quot;</p>
</div>
</div>
</p>
<p><strong>Notes:</strong>&nbsp;</p>
<p><em>More fields may be available via dynamicdata ..</em></p>
</div>
</channel>
</rss>
