The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Adam Thornton <athornton@gmail.com>
To: Clem Cole <clemc@ccc.com>,
	The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] run commands at login in v6 and stty
Date: Mon, 28 Feb 2022 13:03:22 -0700	[thread overview]
Message-ID: <CAP2nic2gEWeWjyr7oXhj4__x3ackjFnaVPX5QxA2PVk4oY6qFA@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2McdPQ=uB-=EcaOf7_W1+CtyhQmsVkpiQ4=F=PPNK0RdQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]

From the Spencer paper:

"In such cases,it is important to go back and fix the kludges. The time is
not wasted; it is an investment in the future"

Yeah, well, that's the problem, isn't it?  Investment in the future is not
incentivized.  The manager needs a win *now* so he can collect his bonus
and then leave for someplace that will pay him more.  Even as a lowly
engineer I've never seen a place where it made financial sense to stick
around.  You'd never get compensation, authority, and responsibility as
fast by being internally promoted as by hopping to the competition across
town.

If the goal were building a sustainable and maintainable ecosystem, then,
sure.  But it isn't.  Good software engineering doesn't pay.  Barfing out a
checklist of feature bullet points that marketing wants pays.

That does suggest that there's some scope for doing this properly in big
Open Source projects--except those, in reality, are almost always driven by
a very few large funders, who have particular features they want and are
willing to pay for.  Shipping those features then becomes the priority, not
keeping the codebase manageable.

I guess it comes down to "hate the game, not the player" on my part and I'm
having a grumpy day.

Adam

[-- Attachment #2: Type: text/html, Size: 2325 bytes --]

  reply	other threads:[~2022-02-28 20:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-28  1:04 Douglas McIlroy
2022-02-28  7:22 ` Rob Pike
2022-02-28 14:07   ` Larry McVoy
2022-02-28 18:47     ` Dan Cross
2022-02-28 19:25       ` Dan Cross
2022-02-28 21:25         ` markus schnalke
2022-02-28 19:26       ` Clem Cole
2022-02-28 20:03         ` Adam Thornton [this message]
2022-02-28 18:18 ` Warner Losh
  -- strict thread matches above, loose matches on Subject: below --
2022-02-27  7:48 Noel Chiappa
2022-02-26 21:45 Brian Walden
2022-02-26 22:16 ` Rob Pike
2022-02-27 20:32 ` Sven Mascheck
2022-02-26 20:39 Will Senn
2022-02-26 21:03 ` Michael Kjörling
2022-02-26 22:49 ` Clem Cole
2022-02-26 23:12   ` Rob Pike
2022-02-27  0:46     ` Clem Cole
2022-02-27 15:01     ` Larry McVoy
2022-02-27 17:10       ` Clem Cole

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=CAP2nic2gEWeWjyr7oXhj4__x3ackjFnaVPX5QxA2PVk4oY6qFA@mail.gmail.com \
    --to=athornton@gmail.com \
    --cc=clemc@ccc.com \
    --cc=tuhs@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).