From: Brad Spencer <brad@anduin.eldar.org>
To: steve jenkin <sjenkin@canb.auug.org.au>
Cc: marc.donner@gmail.com, tuhs@tuhs.org
Subject: [TUHS] Re: LOC [was Re: Re: Re.: Princeton's "Unix: An Oral History": who was in the team in "The Attic"?
Date: Wed, 09 Nov 2022 05:55:42 -0500 [thread overview]
Message-ID: <xon1qqcgzwx.fsf@anduin.eldar.org> (raw)
In-Reply-To: <29942374-F162-43EE-9F65-D51C79B4D7B4@canb.auug.org.au> (message from steve jenkin on Wed, 9 Nov 2022 20:01:25 +1100)
steve jenkin <sjenkin@canb.auug.org.au> writes:
[snip]
> SRE roles & as a discipline has developed, alongside DevOps, into managing & fault finding in large clusters of physical and virtual machines.
>
> Never done it myself, but it’d seem the potential for screw-ups is now infinite and unlimited in time :)
My final $DAYJOB was more DevOps / SRE than system admin which I had
been doing for a long time. And, Very Much Yes, the "potential for
screw-ups" is very much infinite. It seems like that there are a lot of
people messing in areas that they are ill prepared to deal with and tend
to do it poorly at times. Very often they will invent structure that is
just a reinvention of something that already exists because they lack
the background to know what was really available.
> --
> Steve Jenkin, IT Systems and Design
> 0412 786 915 (+61 412 786 915)
> PO Box 38, Kippax ACT 2615, AUSTRALIA
>
> mailto:sjenkin@canb.auug.org.au http://members.tip.net.au/~sjenkin
--
Brad Spencer - brad@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
next prev parent reply other threads:[~2022-11-09 10:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 11:15 [TUHS] " Paul Ruizendaal via TUHS
2022-10-11 13:48 ` [TUHS] " Larry McVoy
2022-10-11 13:59 ` Warner Losh
2022-10-11 19:43 ` Marc Donner
2022-10-11 19:54 ` Larry McVoy
2022-10-11 20:02 ` Michael Kjörling
2022-10-11 20:08 ` Rob Pike
2022-10-11 21:07 ` Dan Cross
2022-10-11 21:41 ` Rob Pike
2022-10-12 6:59 ` arnold
2022-10-12 7:03 ` Michael Kjörling
2022-10-12 7:18 ` Rich Morin
2022-11-29 7:31 ` Joseph Holsten
2022-10-11 20:10 ` Larry McVoy
2022-10-11 20:14 ` Michael Kjörling
2022-10-11 20:33 ` [TUHS] LOC [was " Charles H Sauer (he/him)
2022-11-07 17:50 ` [TUHS] " Warner Losh
2022-11-07 19:57 ` Bakul Shah
2022-11-07 20:11 ` Dan Cross
2022-11-08 18:55 ` Marc Donner
2022-11-09 8:41 ` Dan Cross
2022-11-09 8:49 ` arnold
2022-11-09 20:17 ` Dave Horsfall
2022-11-09 9:01 ` steve jenkin
2022-11-09 10:55 ` Brad Spencer [this message]
2022-11-09 11:56 ` Stuart Remphrey
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=xon1qqcgzwx.fsf@anduin.eldar.org \
--to=brad@anduin.eldar.org \
--cc=marc.donner@gmail.com \
--cc=sjenkin@canb.auug.org.au \
--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).