From: Larry McVoy <lm@mcvoy.com>
To: Michael Kj??rling <e5655f30a07f@ewoof.net>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Re.: Princeton's "Unix: An Oral History": who was in the team in "The Attic"?
Date: Tue, 11 Oct 2022 13:10:25 -0700 [thread overview]
Message-ID: <20221011201025.GJ11780@mcvoy.com> (raw)
In-Reply-To: <8583490b-c7cc-4633-b506-2f16335fd3e2@home.arpa>
On Tue, Oct 11, 2022 at 08:02:41PM +0000, Michael Kj??rling wrote:
> On 11 Oct 2022 12:54 -0700, from lm@mcvoy.com (Larry McVoy):
> > On Tue, Oct 11, 2022 at 03:43:19PM -0400, Marc Donner wrote:
> >> So, come annual review time he gets the most negative possible score.
> >> Why? Because he produced -480K lines of code.
> >
> > Whoever wrote that review should have been fired. Absolutely no clue.
>
> Isn't it relatively well established, though, that IBM culture at
> least for a very long time put heavy emphasis on counting lines of
> source code, and that more SLOC was considered to be better?
That's just stupid. I rewarded more functionality in less or the same
lines of code. Want to add 5K LOC? Great, find 5K LOC of dead code.
My team worked on on the same project for 18 years, the main source
base grew to about 125K LOC and stayed there even though we added
more and more functionality. It is possible.
next prev parent reply other threads:[~2022-10-11 20:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 11:15 [TUHS] " Paul Ruizendaal via TUHS
2022-10-11 13:48 ` [TUHS] " Larry McVoy
2022-10-11 13:59 ` Warner Losh
2022-10-11 19:43 ` Marc Donner
2022-10-11 19:54 ` Larry McVoy
2022-10-11 20:02 ` Michael Kjörling
2022-10-11 20:08 ` Rob Pike
2022-10-11 21:07 ` Dan Cross
2022-10-11 21:41 ` Rob Pike
2022-10-12 6:59 ` arnold
2022-10-12 7:03 ` Michael Kjörling
2022-10-12 7:18 ` Rich Morin
2022-11-29 7:31 ` Joseph Holsten
2022-10-11 20:10 ` Larry McVoy [this message]
2022-10-11 20:14 ` Michael Kjörling
2022-10-11 20:33 ` [TUHS] LOC [was " Charles H Sauer (he/him)
2022-11-07 17:50 ` [TUHS] " Warner Losh
2022-11-07 19:57 ` Bakul Shah
2022-11-07 20:11 ` Dan Cross
2022-11-08 18:55 ` Marc Donner
2022-11-09 8:41 ` Dan Cross
2022-11-09 8:49 ` arnold
2022-11-09 20:17 ` Dave Horsfall
2022-11-09 9:01 ` steve jenkin
2022-11-09 10:55 ` Brad Spencer
2022-11-09 11:56 ` Stuart Remphrey
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=20221011201025.GJ11780@mcvoy.com \
--to=lm@mcvoy.com \
--cc=e5655f30a07f@ewoof.net \
--cc=tuhs@tuhs.org \
/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).