From: Richard Brooksby <richard@harlequin.co.uk>
To: byron@netapp.com (Byron Rakitzis)
Cc: rc@hawkwind.utcs.toronto.edu, schwartz@cse.psu.edu
Subject: Conceptual Integrity (Re: Update for Debian shells/rc-1.4-2)
Date: Tue, 4 Mar 1997 10:22:03 -0500 [thread overview]
Message-ID: <v03010d07af41ed4dde0c@[193.128.93.141]> (raw)
In-Reply-To: <9703031909.AA28293@nova.netapp.com>
Byron Rakitzis wrote:
> That being said, I don't want to see rc unravel because of lack of
> maintenance, and I would like to try to put together the fixes from the
> last while and officially release it, so it gets picked up by the GNU
> distrib and so on.
I am more convinced than ever. Conceptual integrity is central to
product quality. Having a system architect is the most important single
step toward conceptual integrity... After teaching a software
engineering laboratory more than 20 times, I came to insist that student
teams as small as four people choose a manager, and a separate
architect.
-- Fred Brooks, The Mythical Man-Month (20th Anniversary Edition), 1995
Imo, someone needs to be in charge of rc, so that it doesn't get randomly
hacked on by all and sundry. Letting it fly free with the other GNU tools
is almost a guarantee of loss of conceptual integrity. As a long time user
of rc I appreciate its quality, and would like to see quality maintained.
Just voicing my concern.
---
Richard Brooksby <richard@harlequin.co.uk>
Leader, Manager, and Developer / Memory Management / Harlequin
Tel. Int. +44 1954 785451 (voice) +44 1954 785444 (fax)
next prev parent reply other threads:[~1997-03-04 15:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-03-03 19:09 Update for Debian shells/rc-1.4-2 Byron Rakitzis
1997-03-04 3:34 ` David Luyer
1997-03-04 3:51 ` Soren Dayton
1997-03-04 15:22 ` Richard Brooksby [this message]
1997-03-04 17:33 ` Peter Koch
1997-03-04 19:08 ` Scott Schwartz
1997-03-04 16:57 Conceptual Integrity (Re: Update for Debian shells/rc-1.4-2) Byron Rakitzis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='v03010d07af41ed4dde0c@[193.128.93.141]' \
--to=richard@harlequin.co.uk \
--cc=byron@netapp.com \
--cc=rc@hawkwind.utcs.toronto.edu \
--cc=schwartz@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).