From: John Cowan <cowan@ccil.org>
To: Jon Steinhart <jon@fourwinds.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] ching in Unix
Date: Sat, 30 Jan 2021 02:28:41 -0500 [thread overview]
Message-ID: <CAD2gp_Re7gmF-93_LchNY77V=5v5crCyNUHAyGs79ASLnQLzeQ@mail.gmail.com> (raw)
In-Reply-To: <202101282305.10SN5wxt164484@darkstar.fourwinds.com>
[-- Attachment #1: Type: text/plain, Size: 1575 bytes --]
On Thu, Jan 28, 2021 at 6:06 PM Jon Steinhart <jon@fourwinds.com> wrote:
> I have always found the I Ching to be an invaluable tool for
> making difficult management decisions.
>
Or any other kind of decisions.
Some of you may find amusing my (regrettably incomplete) "The Unix Power
Classic: A book about the Unix Way and its power" at <
http://vrici.lojban.org/~cowan/upc/>. Section 41 seems to be the most
popular:
Thoughtful hackers hear about Unix
and try to use it.
Ordinary hackers hear about Unix
and mess about with it a little.
Thoughtless hackers hear about Unix
and crack wise about it.
It wouldn't be Unix
if there weren't wisecracks about it.
So we establish the following rules:
The most brilliant Unix seems the most obscure.
Advanced Unix seems like retrocomputing.
The most powerful code seems like just loops and conditionals.
The clearest code seems to be opaque.
The sharpest tools seem inadequate.
Solid code seems flaky.
Stable code seems to change.
Great methodologies don't have boundaries.
Great talent doesn't code fast.
Great music makes no sound.
The ideal elephant has no shape.
The Unix Way has no name.
Yet for just this reason
it brings things to perfection.
John Cowan http://vrici.lojban.org/~cowan cowan@ccil.org
The native charset of SMS messages supports English, French, mainland
Scandinavian languages, German, Italian, Spanish with no accents, and
GREEK SHOUTING. Everything else has to be Unicode, which means you get
only 70 16-bit characters in a text instead of 160 7-bit characters.
[-- Attachment #2: Type: text/html, Size: 3221 bytes --]
next prev parent reply other threads:[~2021-01-30 7:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 21:45 Warren Toomey
2021-01-28 22:01 ` John Floren
2021-01-28 22:10 ` George Michaelson
2021-01-28 22:12 ` John Floren
2021-01-28 22:32 ` George Michaelson
2021-01-28 23:05 ` Jon Steinhart
2021-01-30 7:28 ` John Cowan [this message]
2021-01-30 7:31 ` Adam Thornton
2021-03-28 6:29 ` scj
2021-03-28 21:56 ` Noel Hunt
2021-04-10 20:32 ` Sean Dwyer via TUHS
2021-03-28 22:31 Norman Wilson
2021-03-29 2:06 ` Noel Hunt
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='CAD2gp_Re7gmF-93_LchNY77V=5v5crCyNUHAyGs79ASLnQLzeQ@mail.gmail.com' \
--to=cowan@ccil.org \
--cc=jon@fourwinds.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).