The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Ed Carp <erc@pobox.com>
To: Brad Spencer <brad@anduin.eldar.org>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] more about Brian...
Date: Mon, 7 Feb 2022 22:22:44 -0700	[thread overview]
Message-ID: <CACYmRNCuYPZQFY=45V5dyw28Z4Tpz-4WH=2PSCpov75cF+TPoQ@mail.gmail.com> (raw)
In-Reply-To: <xonh79cas2e.fsf@anduin.eldar.org>

And that reminds me of the old "Three Envelopes" joke:


A new CEO takes his seat at the helm of a large corporation
He finds three envelopes on his desk, numbered 1 to 3, and a note.

"Dear successor,
On this desk you find 3 envelopes that will help you in times of a
crisis. Open them only in the order they are numbered, and only when
you face a crisis that you cannot manage.
Best of luck".

He stores them in his safe and goes to work. But the economy isn't
picking up, the corporation isn't doing too well and the board wants
an explanation. He decides it's time for the first envelope. He rips
it open and reads:

"Blame your predecessor".

And he does. He steps up at the press conference and blames everything
on the shortcomings and nearsightedness of his predecessor and how he
just needs a bit more time to turn things around. Everyone is pleased
and he remains CEO.

But after a while, the displeasure isn't waning and the corporation
isn't doing any better. Another press conference is held and he rips
open the next envelope:

"Call for reorganizations".

And he does. He presents a great reorganization project with no stone
remaining unturned, this will surely improve productivity and move the
corporation into the future. Everyone's so busy reorganizing that
nobody can even notice how the corporation is running worse and worse,
until there's really no way to cover it up anymore. He reaches for the
third and last envelope, hoping for the great reveal that will save
him once and for all. He rips it open and reads:

"Prepare 3 envelopes and a note".


On 2/6/22, Brad Spencer <brad@anduin.eldar.org> wrote:
> Will Senn <will.senn@gmail.com> writes:
>
> [snip]
>
>>> I've done this and I've employed people who have done this.  We're
>>> a dieing breed, the focus seems to be on programming languages and
>>> tools for idiots.  People don't want to learn the discipline it takes
>>> to work with malloc()/free().  It's sad.
>>
>> I completely agree. This is ridiculous. Do modern programmer's seriously
>> think that the old code wasn't complex or robust? Sheesh, there's code
>> out there that has run through more millions of transactions an hour for
>> more years than most of these folks have been alive. There's also code
>> that's been running without any updates, for decades. Most code written
>> by the newbreed won't run for a month without surfacing dozens of bugs.
>> Margaret Hamilton would prolly have some choice words for these folks.
>
> This would appear to be a Not Unix conversation... but...
>
> So...  the idea that code would run that long was not at all valued at
> my last job.  The management found it simpler and better (for some
> definition of better) to just reinvent everything every 3 to 6 years.
> In the mean time, the languages used would change.  The idea that one
> would "have to waste time" figuring out how to use malloc() and free()
> properly was not looked upon well when the development time would be
> better spend solving the needed higher level problems.  In other words
> there literally was no interest in creating code that was going to be
> maintained for more than about 6 years and in a lot of cases would not
> be maintained more than 3 or even 1 year.
>
> To bring this back to Unix somewhat...  When I started there, everything
> was a Solaris based private cloud (SmartOS by Joyent) running Java apps.
> In the 5 years I was there, the move was from Java to Go, due to the
> licensing changes that Oracle made to Java and then a move to
> containers.  SmartOS has a container technology that is sort of like
> Docker, but since the majority of the containers in the world that
> people know about are fully Docker in some form with Linux it wasn't as
> compatible as required so SmartOS was dumped and everything was redone
> in Azure public cloud with Linux and as much of the native Azure stuff
> as they could stand to use.  Make everything "green field" all of the
> time, or something....
>
> I didn't really agree with much of this, but I became pretty mercenary
> as I got old and the place paid well.
>
>
>
>
>
>
>
> --
> Brad Spencer - brad@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
>

  reply	other threads:[~2022-02-08  5:23 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31 20:46 [TUHS] ratfor vibe Will Senn
2022-02-01 15:37 ` arnold
2022-02-01 15:52   ` Ralph Corderoy
2022-02-01 16:58     ` Clem Cole
2022-02-01 17:02     ` silas poulson
2022-02-02  7:47     ` arnold
2022-02-03  5:47       ` [TUHS] more about Brian Rich Morin
2022-02-03  7:44         ` markus schnalke
2022-02-03  8:18           ` Rich Morin
2022-02-04  2:23           ` Adam Thornton
2022-02-04  2:34             ` [TUHS] more about Brian... [really Rust] Jon Steinhart
2022-02-04 13:07               ` Thomas Paulsen
2022-02-04 23:18               ` Dan Cross
2022-02-04  3:28             ` [TUHS] more about Brian Dan Stromberg
2022-02-04  5:11             ` Rich Morin
2022-02-04 21:22               ` [TUHS] Go vs. Rust, and etc. (was: more about Brian...) Greg A. Woods
2022-02-04 21:37                 ` Richard Salz
2022-02-04 22:32                   ` Steffen Nurpmeso
2022-02-04 23:05                   ` Thomas Paulsen
2022-02-04 23:15                   ` Seth J. Morabito
2022-02-05  1:41                     ` Adam Thornton
2022-02-04  7:38             ` [TUHS] more about Brian Andy Kosela
2022-02-04  8:10               ` Steve Nickolas
2022-02-04  8:44                 ` markus schnalke
2022-02-04  9:16                   ` Steve Nickolas
2022-02-04 18:54                 ` John Cowan
2022-02-04 19:45                   ` Thomas Paulsen
2022-02-04 20:28                     ` Hellwig Geisse
2022-02-04 21:03                       ` Jim Capp
2022-02-04 22:30                         ` Steffen Nurpmeso
2022-02-04 22:25                       ` Steffen Nurpmeso
2022-02-06  0:56                       ` Larry McVoy
2022-02-06  1:10                         ` Will Senn
2022-02-06  4:52                           ` Rob Pike
2022-02-06  4:58                             ` Dan Halbert
2022-02-06  5:06                             ` Will Senn
2022-02-06  6:19                             ` Ed Carp
2022-02-06  6:27                               ` Rob Pike
2022-02-06  6:40                                 ` Stuart Remphrey
2022-02-06  6:44                                 ` Bakul Shah
2022-02-06 19:08                                   ` Steffen Nurpmeso
2022-02-06 12:52                                 ` Ralph Corderoy
2022-02-06 13:14                                 ` Ed Carp
2022-02-06 14:13                                   ` Dan Cross
2022-02-06 14:15                                   ` Larry McVoy
2022-02-06 16:31                                     ` Warner Losh
2022-02-06 18:36                                     ` [TUHS] more about Brian... [ really GC vs malloc/free languages ] Jon Steinhart
2022-02-06 19:27                                     ` Jon Steinhart
2022-02-06 19:33                                       ` Warner Losh
2022-02-06 19:37                                         ` Jon Steinhart
2022-02-06 20:21                                           ` [TUHS] COFF is over there Ralph Corderoy
2022-02-06 16:16                           ` [TUHS] more about Brian Brad Spencer
2022-02-08  5:22                             ` Ed Carp [this message]
2022-02-03 18:57       ` [TUHS] ratfor vibe silas poulson
2022-02-04  8:26         ` arnold
2022-02-04 19:41           ` John Cowan
2022-02-10 15:18       ` Ralph Corderoy
2022-02-03  4:00 ` Will Senn
2022-02-03  4:31   ` Al Kossow
2022-02-03  5:16     ` Warner Losh
2022-02-03 20:00   ` Adam Thornton
2022-02-04  6:06     ` Ori Idan
2022-02-04 17:35       ` Adam Thornton
2022-02-04 17:44         ` Will Senn

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='CACYmRNCuYPZQFY=45V5dyw28Z4Tpz-4WH=2PSCpov75cF+TPoQ@mail.gmail.com' \
    --to=erc@pobox.com \
    --cc=brad@anduin.eldar.org \
    --cc=tuhs@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).