The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Ruizendaal via TUHS <tuhs@tuhs.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re.: Princeton's "Unix: An Oral History": who was in the 	team in "The Attic"?
Date: Tue, 11 Oct 2022 13:15:38 +0200	[thread overview]
Message-ID: <992562BA-E21F-4542-A50B-6CFE8F7ACE86@planet.nl> (raw)


> Has anyone roughly calculated “man years” spent developing Unix to 1973 or 1974?
> Under 25 "man-years”? (person years now)

I cannot find the message at the moment (TUHS mail archive search is not working anymore?), but I recall that Doug McIlroy mentioned on this list that 1973 was a miracle year, where Ken & Dennis wrote and debugged over 100,000 lines of code between them. In software, “man year” is an elastic yardstick...

There is also this anecdote by Andy Herzfeld:

===
Quickdraw, the amazing graphics package written entirely by Bill Atkinson, was at the heart of both Lisa and Macintosh. "How many man-years did it take to write QuickDraw?", the Byte magazine reporter asked Steve [Jobs].

Steve turned to look at Bill. "Bill, how long did you spend writing Quickdraw?"

"Well, I worked on it on and off for four years", Bill replied.

Steve paused for a beat and then turned back to the Byte reporter. "Twenty-four man-years. We invested twenty-four man-years in QuickDraw."

Obviously, Steve figured that one Atkinson year equaled six man years, which may have been a modest estimate.
===

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”.



             reply	other threads:[~2022-10-11 11:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11 11:15 Paul Ruizendaal via TUHS [this message]
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                 ` [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=992562BA-E21F-4542-A50B-6CFE8F7ACE86@planet.nl \
    --to=tuhs@tuhs.org \
    --cc=pnr@planet.nl \
    /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).