From: Robert Dewar <dewar@gnat.com>
Subject: Re: Converting Ada Tasks To VxWorks Tasks?
Date: 2000/04/16
Date: 2000-04-16T00:00:00+00:00 [thread overview]
Message-ID: <8dc9t9$lij$1@nnrp1.deja.com> (raw)
In-Reply-To: xEZJ4.334$d21.35336@elnws01
In article <xEZJ4.334$d21.35336@elnws01>,
"Michael Hartsough" <Michael-Hartsough@mediaone.net> wrote:
h
> Won't work. Official policy is that nobody's indispensible.
> especially an Ada & Multitasking Advocate. ;^)
A bit off topic, but I really feel like making a comment on
this point. I agree that any company should have an official
policy that no one is indispensable, and should orient the
structure of development according to this point. After all
if an indispensable person is in a fatal accident, the company
can be very seriously impacted.
This is one of the reasons at Ada Core Technologies that I have
very strongly insisted on avoiding a situation where only one
person knows some code, and no one else can touch it. There
are two approaches that help:
1. Avoid the use of author's names on units, or anything else
that encourages the notion of ownership. Some formal
configuration management procedures actually encourage
or even insist on the idea that only one person can
control changes to a unit, but I think that's a very
bad idea.
2. Insist on a highly uniform coding style, so that anyone
feels comfortable with anyone else's code.
You know you are beginning to succeed here when A writes
some chunk of code, or perhaps a whole unit, and B fixes
a bug in it, and A's reaction is "great, that's one bug
I don't have to fix", instead of "Hey! What's B doing
mucking in *my* code?" I have been in far too many situations
at other companies where the second reaction is typical, and
where individuals have idiosyncratic coding styles that tend
to discourage the situation in the first place.
That being said, I find it extraordinary, and extremely
misguided that for many large companies, the policy of
avoiding indispensibility gets transmogrified to a viewpoint
that everyone is interchangable, and that, for example, if
you want to cut your work force, it doesn't matter who goes.
The fact remains that productivities vary hugely in our field,
and management failing to note this fact when they decide who
to retain is a very serious problem in companies that make
this fundamental mistake.
Robert Dewar
Ada Core Technologies
Sent via Deja.com http://www.deja.com/
Before you buy.
next prev parent reply other threads:[~2000-04-16 0:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-13 0:00 Converting Ada Tasks To VxWorks Tasks? Michael Hartsough
2000-04-13 0:00 ` Ted Dennison
2000-04-14 0:00 ` dale
2000-04-15 0:00 ` Robert Dewar
2000-04-14 0:00 ` Robert A Duff
2000-04-14 0:00 ` Michael Hartsough
2000-04-14 0:00 ` Tucker Taft
2000-04-15 0:00 ` Michael Hartsough
2000-04-14 0:00 ` Jeff Carter
2000-04-14 0:00 ` Michael Hartsough
2000-04-14 0:00 ` Ted Dennison
2000-04-14 0:00 ` Marin D. Condic
2000-04-14 0:00 ` Stanley R. Allen
2000-04-15 0:00 ` Michael Hartsough
2000-04-16 0:00 ` Robert Dewar [this message]
2000-04-16 0:00 ` Jeff Carter
2000-04-16 0:00 ` Michael Hartsough
2000-04-15 0:00 ` Jeff Carter
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox