From: segaloco via TUHS <tuhs@tuhs.org>
To: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: Honor declined
Date: Wed, 06 Mar 2024 21:45:11 +0000 [thread overview]
Message-ID: <4pgV5_iD_8o-bsF8_GfxuR5jG49CxGl-FALoO7a5G5k0Xwtaq39zkATBU8O-mIORXpt4U_kI_pLokc5f-qrQo2GP6JdI3N2Df_b8UUqhl9k=@protonmail.com> (raw)
In-Reply-To: <CAKH6PiW_sakBxgwP2kHRDBQMucapp59v9szVn+8U+B-4cZUQ3Q@mail.gmail.com>
On Wednesday, March 6th, 2024 at 11:53 AM, Douglas McIlroy <douglas.mcilroy@dartmouth.edu> wrote:
> After Multics, I ran interference to keep our once-burned higher management from frowning too much on further operating-system research.
>
> Doug
This alone is an all-too-valuable skill that contributes to the cultural success of countless projects. Great ideas can too often die on the vine when the upper echelons have quite different opinions of where time and effort should be placed, and I am glad that in my own career I likewise work with understanding immediate supervisors and business analysts that go to bat for our needs and concerns. The importance of a supportive workplace culture in which work is genuinely valued and defended cannot be understated.
- Matt G.
next prev parent reply other threads:[~2024-03-06 21:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 14:55 [TUHS] " Douglas McIlroy
2024-03-06 15:03 ` [TUHS] " Brantley Coile
2024-03-06 19:53 ` Douglas McIlroy
2024-03-06 20:06 ` Will Senn
2024-03-06 21:45 ` segaloco via TUHS [this message]
[not found] ` <CAMP=X_mSvku8KCweaeeDQMNR0hXaegdjt_gH1Cu6GfRNStfz2Q@mail.gmail.com>
2024-03-07 1:33 ` segaloco via TUHS
2024-03-06 16:53 Noel Chiappa
2024-03-06 18:33 ` Brantley Coile
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='4pgV5_iD_8o-bsF8_GfxuR5jG49CxGl-FALoO7a5G5k0Xwtaq39zkATBU8O-mIORXpt4U_kI_pLokc5f-qrQo2GP6JdI3N2Df_b8UUqhl9k=@protonmail.com' \
--to=tuhs@tuhs.org \
--cc=segaloco@protonmail.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).