From: Rich Morin <rdm@cfcl.com>
To: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Re.: Princeton's "Unix: An Oral History": who was in the team in "The Attic"?
Date: Wed, 12 Oct 2022 00:18:44 -0700 [thread overview]
Message-ID: <62BF9FE1-F664-4CFE-B307-8FA987A14742@cfcl.com> (raw)
In-Reply-To: <1e7be6ed-5b2f-41b8-944f-05d1f98e6125@home.arpa>
I recall hearing about a new hire at IBM who was tasked with working on the JCL processing code. After looking it over, he decided to rewrite it using compiler-compiler technology. The result worked, was about 250 KLOC smaller than the original, and was accepted.
However, at review time the employee received an absolutely terrible review. Seems he had generated a really substantial negative amount of code. Story I heard was that he was soon picked up by IBM Labs...
-r
next prev parent reply other threads:[~2022-10-12 7:20 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 [this message]
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=62BF9FE1-F664-4CFE-B307-8FA987A14742@cfcl.com \
--to=rdm@cfcl.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).