The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: don@DonHopkins.com (Don Hopkins)
Subject: SGI Software Usability II (IRIX 5.1 memo)
Date: Thu, 12 Oct 2017 16:16:38 +0200	[thread overview]
Message-ID: <09E69ADC-17BC-4944-A3D6-BB553C6F2333@gmail.com> (raw)
In-Reply-To: <20171012140021.GK17135@mcvoy.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1860 bytes --]

The version of the embarrassing memo on the University of Virginia CS415 reading list that I linked to is an email response from the author Tom Davis, posted to comp.sys.next.advocacy on 25 Apr 1994, which includes his extremely interesting inline comments that he added after the memo was leaked, following up about what happened at SGI in response to the leak! 

http://www.cs.virginia.edu/~cs415/reading/irix-bloat.txt <http://www.cs.virginia.edu/~cs415/reading/irix-bloat.txt>

SGI the institution was embarrassed, but I don’t think Tom Davis has anything to be embarrassed about personally: he handled it well and honestly, told the unvarnished truth to management, which had a positive effect, and his candid write-up and response now serves as a great example for students learning how things work in the real world! 

It should be required reading in all computer science programs (and management programs too)!

-Don


> On 12 Oct 2017, at 16:00, Larry McVoy <lm at mcvoy.com> wrote:
> 
> I strongly suspect it was true, Tom Davis was an SGI employee as
> were the other people mentioned.  
> 
> On Thu, Oct 12, 2017 at 02:04:43PM +0100, Michael-John Turner wrote:
>> Hi,
>> 
>> I came across this on Lobsters[1] today and thought it may be of interest to
>> the list:
>> http://www.art.net/~hopkins/Don/unix-haters/tirix/embarrassing-memo.html
>> 
>> It appears to be an internal SGI memo that's rather critical of IRIX 5.1.
>> Does anyone know if it's true?
>> 
>> [1] https://lobste.rs/
>> 
>> Cheers, MJ
>> -- 
>> Michael-John Turner * mj at mjturner.net * http://mjturner.net/
> 
> -- 
> ---
> Larry McVoy            	     lm at mcvoy.com             http://www.mcvoy.com/lm 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171012/7121637c/attachment.html>


  reply	other threads:[~2017-10-12 14:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-12 13:04 Michael-John Turner
     [not found] ` <AC831F18-D52F-4C0F-9E31-E4C7CD3F4A1E@gmail.com>
2017-10-12 13:43   ` Don Hopkins
2017-10-12 14:00 ` Larry McVoy
2017-10-12 14:16   ` Don Hopkins [this message]
2017-10-12 14:55     ` Don Hopkins
2017-10-12 14:59       ` Larry McVoy
2017-10-12 15:09         ` Don Hopkins
2017-10-12 15:20           ` Don Hopkins
2017-10-12 14:22   ` AT&T taking over Sun: Panic! Don Hopkins
2017-10-13 15:59   ` SGI Software Usability II (IRIX 5.1 memo) Jose R. Valverde

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=09E69ADC-17BC-4944-A3D6-BB553C6F2333@gmail.com \
    --to=don@donhopkins.com \
    /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).