Computer Old Farts Forum
 help / color / mirror / Atom feed
From: clemc at ccc.com (Clem Cole)
Subject: [COFF] [SPAM] Re: [TUHS] Algol 68 and Unix (was cron and at ...)
Date: Fri, 18 Dec 2020 10:46:10 -0500	[thread overview]
Message-ID: <CAC20D2OEb7Zii0DJsQm_kARnBf8nCdna67cvbFjXA-yjnSJLkw@mail.gmail.com> (raw)
In-Reply-To: <20201218144332.GH13368@mcvoy.com>

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

Excellent!
ᐧ

On Fri, Dec 18, 2020 at 9:43 AM Larry McVoy <lm at mcvoy.com> wrote:

> On Thu, Dec 17, 2020 at 04:10:03PM -0500, Clem Cole wrote:
> > On Thu, Dec 17, 2020 at 1:00 PM Larry McVoy <lm at mcvoy.com> wrote:
> >
> > > I think it is part of being really smart, it's a puzzle for them and
> they
> > > "win" if they can do something clever.  I always replied "It is write
> once,
> > > read many.  Optimize for reads".
> > >
> > Amen to that bro.
> >
> > As a side note, I will say there is another vector to this same curse.
> > It's the new guy coming into the project and deciding what is there is
> > crap, they can not understand and they can do a better job.
>
> Source management to the rescue.  I hired an extremely smart guy (he
> reads papers on string theory, the physics ones, for fun).  Taught him
> how to use our tools.  Gave him a bug to fix.  He looks at the source
> file and goes "This is crap, I'm gonna rewrite it so it is clean".
> Then remembers I showed him how he could see how the file evolved.
> So he looks at the first version of the file.  It is *exactly* what he
> was going to write.  Huh.  He starts going through the history.  Oh,
> this wart is for IRIX.  This wart is for windows 2000 that reuses PIDs
> right away.  This wart is for NFS.  Etc.
>
> In the end, he added another wart to fix the bug and left the file alone.
> I did say he was smart.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20201218/b2caefed/attachment.htm>


  reply	other threads:[~2020-12-18 15:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAKH6PiVLgdPVEGvGfyVAwNMz66=0huVyvRY90E+PduwG4ssVRQ@mail.gmail.com>
     [not found] ` <0EA02917-243E-4612-9F7E-D370EE0A7C2E@ronnatalie.com>
     [not found]   ` <20201217143558.GD13268@mcvoy.com>
2020-12-17 15:22     ` [COFF] " clemc
2020-12-17 15:50       ` [COFF] [SPAM] " lm
2020-12-17 17:57         ` imp
2020-12-17 18:00           ` lm
2020-12-17 18:30             ` [COFF] " 
2020-12-17 21:10             ` [COFF] [SPAM] " clemc
2020-12-18 14:43               ` lm
2020-12-18 15:46                 ` clemc [this message]
2020-12-18 17:41                 ` tytso
2020-12-18 19:24                   ` [COFF] " lm

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=CAC20D2OEb7Zii0DJsQm_kARnBf8nCdna67cvbFjXA-yjnSJLkw@mail.gmail.com \
    --to=coff@minnie.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).