From: "Alan D. Salewski" <ads@salewski.email>
To: "TUHS (The Unix Heritage Society)" <tuhs@tuhs.org>
Subject: [TUHS] Re: Unix Systems Administration Texts
Date: Wed, 01 Mar 2023 17:57:11 -0500 [thread overview]
Message-ID: <eca796aa-85cf-49a6-a748-9204d99a39fe@app.fastmail.com> (raw)
In-Reply-To: <CAEoi9W7KUYn2Z1jESPGK=qU5ysF3jmJk5R+D_s03njjFshi--w@mail.gmail.com>
On Tue, Feb 28, 2023, at 21:34, Dan Cross wrote:
> On Tue, Feb 28, 2023 at 8:38 PM Will Senn <will.senn@gmail.com> wrote:
>> I'm curious about the experience of those of y'all who actually used them. Were there any early standouts and why did they stand out?
>
> This is not going to be popular, but...
>
>> Nemeth, E., Synder, G., & Seebass, S. (1989). UNIX System Administration Handbook (5th edition is another fatty)
>
> This book gave me some terrible advice when I was very young and impressionable.
>
> In there somewhere it says something about not doing something unless
> you're prepared to do it right lest one spend more time working around
> a work-around than one would have spent just doing it well in the
> first place.
>
> The conclusion is, of course, true, but the admonition ignores all
> sorts of externalities, like waiting users. And in some cases it could
> really lead to paralysis
[...]
> Hopefully nowadays we have a better appreciation of the power of
> incrementalism; those grand plans for the perfect system rarely come
> to fruition. It's better to be flexible and make small, impactful
> changes along the way towards a better system, always being mindful of
> and tamping down encroaching entropy.
>
> - Dan C.
Yeah, good or bad advice at just the right time can have quite an
impact.
In the under-celebrated "Minimal Perl"[0], Tim Maher notes in the
last paragraph of section 5.8:
<quote>
In your own career, I'd advise you to develop an appreciation an
appreciation and an aptitude for both the /quick-and-dirty/ and
/elegant-and-formal/ styles of programming, and to cultivate the
ability to produce either kind on demand, as circumstances
warrant.
</quote>
Seems obvious, in retrospect -- but of course many things do with
the benefit of hindsight. For me, that articulated something that I
sensed was the right way to approach things, but was contrary to
much of the one-dimensional advice I had received up to that
point. It pairs well with one of the "lesser tenets" noted by
Gancarz: "Look for the 90 percent solution"[1].
In my own career, I've found I can often use the quick-and-dirty
approach to buy myself time to afford the "detour to build the
tools"[2] that could not be justified (to others) up-front. And
nothing gets it done faster than a shell script. Five or ten scrappy
N-line shell scripts that get the job done sub-optimally, and
lacking any real thought toward usability or generality buy time to
build better tools (usually more, better-written shell scripts). And
sometimes a scrappy script is "good enough" (for years, even).
-Al
[0] Minimal Perl for Unix People and Linux People
by Tim Maher
Forward by Damian Conway
Manning 2007
p. 175
ISBN-10: 1-932394-50-8
[1] The Unix Philosophy
by Mike Gancarz
Digital Press 1995
p. 117
ISBN-10: 1-55558-123-4
[2] [McIlroy78] The Bell System Technical Journal. Bell Laboratories.
M. D. McIlroy, E. N. Pinson, and B. A. Tague.
"Unix Time-Sharing System Forward". 1978. 57 (6, part 2). p. 1902.
https://archive.org/details/bstj57-6-1899/page/n3/mode/2up
Also quoted in ESR's "The Art of Unix Programming"
Addison-Wesley 2004
p. 12
ISBN-13: 9-780131-429017
https://www.catb.org/~esr/writings/taoup/html/ch01s06.html
--
a l a n d. s a l e w s k i
ads@salewski.email
salewski@att.net
https://github.com/salewski
next prev parent reply other threads:[~2023-03-01 22:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 1:38 [TUHS] " Will Senn
2023-03-01 2:34 ` [TUHS] " Dan Cross
2023-03-01 3:24 ` Larry McVoy
2023-03-01 9:03 ` steve jenkin
2023-03-01 18:34 ` Pete Wright via TUHS
2023-03-01 22:57 ` Alan D. Salewski [this message]
2023-03-02 0:41 ` Adam Thornton
2023-03-02 2:02 ` Jan Schaumann via TUHS
2023-03-01 8:34 ` steve jenkin
2023-03-01 18:41 ` Warner Losh
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=eca796aa-85cf-49a6-a748-9204d99a39fe@app.fastmail.com \
--to=ads@salewski.email \
--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).