From: imp at bsdimp.com (Warner Losh)
Subject: [COFF] [SPAM] Re: [TUHS] Algol 68 and Unix (was cron and at ...)
Date: Thu, 17 Dec 2020 10:57:13 -0700 [thread overview]
Message-ID: <CANCZdfqw635x_P2VPK-9a3fbUu6oqMbqumh-JgAgHU15MNvTgg@mail.gmail.com> (raw)
In-Reply-To: <20201217155039.GA13368@mcvoy.com>
On Thu, Dec 17, 2020 at 8:50 AM Larry McVoy <lm at mcvoy.com> wrote:
> I told my people that it doesn't matter who wrote it 6 months from now,
> even if it was you, you are going to have to relearn the code to fix a
> bug in it.
>
This goes double or triple for open source. 6 months from now, the odds are
50/50 the original contributor is busy, unavailable at the moment or
otherwise gone if it wasn't one of the current top 20 contributors.
Clever is almost always wrong... It's only right if the code is performance
critical and the cleverness gives better performance in a meaningful way.
And even then the bias is against being too clever.
Warner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20201217/7996943c/attachment-0001.htm>
next prev parent reply other threads:[~2020-12-17 17:57 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 [this message]
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
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=CANCZdfqw635x_P2VPK-9a3fbUu6oqMbqumh-JgAgHU15MNvTgg@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).