From: Warner Losh <imp@bsdimp.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: LOC [was Re: Re: Re.: Princeton's "Unix: An Oral History": who was in the team in "The Attic"?
Date: Mon, 7 Nov 2022 10:50:33 -0700 [thread overview]
Message-ID: <CANCZdfoEg_++R7ANoU=Cg5Uzn5x-MUXm5wpk1zsAurOV_Be9Gg@mail.gmail.com> (raw)
In-Reply-To: <0db171e4-7efe-8c00-bb30-a6f914cf9911@technologists.com>
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
On Tue, Oct 11, 2022 at 2:34 PM Charles H Sauer (he/him) <
sauer@technologists.com> wrote:
> On 10/11/2022 3:14 PM, Michael Kjörling wrote:
> > On 11 Oct 2022 13:10 -0700, from lm@mcvoy.com (Larry McVoy):
> >>> 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.
> >
> > You're getting no argument from me there.
> >
>
> It was likely true that some parts of IBM put heavy emphasis on LOC, but
> as Marc points out, that wasn't true in Research. I don't remember heavy
> LOC emphasis in AIX groups, and I suspect even in Boca (OS/2) there was
> not "heavy" emphasis.
>
Speaking of "just stupid"
Word on the street is that Elon Musk stack ranked the engineers by lines of
code
over the last year (source: https://ma.nu/blog/bye-twitter) and layed off
the bottom
performers in terms of LoC...
Not 100% sure this is legit, since some tweets about it have been deleted.
Warners
[-- Attachment #2: Type: text/html, Size: 1725 bytes --]
next prev parent reply other threads:[~2022-11-07 17:52 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
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 ` Warner Losh [this message]
2022-11-07 19:57 ` [TUHS] " 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='CANCZdfoEg_++R7ANoU=Cg5Uzn5x-MUXm5wpk1zsAurOV_Be9Gg@mail.gmail.com' \
--to=imp@bsdimp.com \
--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).