The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Marc Donner <marc.donner@gmail.com>
To: Warner Losh <imp@bsdimp.com>
Cc: Paul Ruizendaal <pnr@planet.nl>,
	The Eunuchs Hysterical Society <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 15:43:19 -0400	[thread overview]
Message-ID: <CALQ0xCA8djfEVxvxkmtwg0uE+YCEYNh1n7etbuJS=9+3=qPq7A@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfrY0DHVC+VNcJGKcyYNfHN0uM=OP8z3wm-2dEsDVd8RqA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2496 bytes --]

A friend of mine at IBM Research told me the following experience from his
early career.

He was hired to join the MVS development team in Poughkeepsie (or
Endicott?) right out of school.

He got the "new kid" assignment - maintaining the JCL interpreter.  500K
lines of H Assembler (might have been G Assembler ... disremember).

The job was to take bug tickets, analyze them, and respond with either a
fix or a rejection.

After a bit of this he thinks to himself, "Self, this is a programming
language, but badly implemented in assembler with lots of copy-paste
crap."  He had studied computer science in college, so he knew something
about compiler implementation.

So he builds a set of parser tables using what he learned from the Dragon
Book and implements a new JCL interpreter in PL/1 (or PL/S?).  About 20K
LOC.

The new JCL interpreter is faster, though that doesn't really matter.  More
importantly, it also closes hundreds of bugs that arose from the fact that
many of subcommands had suboptions with variant implementations, even
though they were *supposed* to be the same suboption.

So, come annual review time he gets the most negative possible score.
Why?  Because he produced -480K lines of code.

So he transferred to the Research Division where his skills were more
valued and where I met him.
=====
nygeek.net
mindthegapdialogs.com/home <https://www.mindthegapdialogs.com/home>


On Tue, Oct 11, 2022 at 10:00 AM Warner Losh <imp@bsdimp.com> wrote:

>
>
> On Tue, Oct 11, 2022 at 7:49 AM Larry McVoy <lm@mcvoy.com> wrote:
>
>> On Tue, Oct 11, 2022 at 01:15:38PM +0200, Paul Ruizendaal via TUHS wrote:
>> > There is also another anecdote involving Atkinson. At some point all
>> Apple programmers had to file a weekly report with how many lines of code
>> they wrote that week. After a productive week of refactoring and
>> optimising, he filed a report saying "minus 2,000 lines".
>>
>> We bonused people for that.
>>
>
> I love commits like this, thought it wasn't refactoring so much as
> deleting obsolete code...
>
> commit c09981f1422ef0d44042dacc5d1265392fba39f1
> Author: Warner Losh <imp@FreeBSD.org>
> Date:   Thu Dec 30 20:56:09 2021 -0700
>
>     mips: Remove sys/mips
>
>     Remove sys/mips as the next step of decomissioning mips from the tree.
>     Remove mips special cases from the kernel make files. Remove the mips
>     specific linker scripts.
>
>     Sponsored by:           Netflix
> ...
>  594 files changed, 4 insertions(+), 134,562 deletions(-)
>

[-- Attachment #2: Type: text/html, Size: 4929 bytes --]

  reply	other threads:[~2022-10-11 19:44 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 [this message]
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                 ` [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='CALQ0xCA8djfEVxvxkmtwg0uE+YCEYNh1n7etbuJS=9+3=qPq7A@mail.gmail.com' \
    --to=marc.donner@gmail.com \
    --cc=imp@bsdimp.com \
    --cc=pnr@planet.nl \
    --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).