The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Adam Thornton <athornton@gmail.com>
To: Jon Steinhart <jon@fourwinds.com>,
	The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Happy birthday Morris worm [ really programming education ]
Date: Fri, 15 Nov 2019 17:49:29 -0500	[thread overview]
Message-ID: <CAP2nic1ysr11mL3WHPf9Tqag2PHaoZUY3gvB9+_W-LDh6yTTKQ@mail.gmail.com> (raw)
In-Reply-To: <201911131802.xADI2fxE752068@darkstar.fourwinds.com>

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

On Wed, Nov 13, 2019 at 1:03 PM Jon Steinhart <jon@fourwinds.com> wrote:

> arnold@skeeve.com writes:
> Programming today is taught as if it consists of importing libraries
> and gluing function calls together.
>

To be fair, this is basically what modern software development in
enterprise settings is.  Thing is, you don’t need a CS degree for that;
it’s a completely artificial barrier to entry.  You need an
apprenticeship.  That’s even kind of acknowledged, in that by your third
job, no one cares where or if you went to school or what for.

Anyway, my question for you all is, how do we as seasoned practitioners
> leverage our experience to contribute to the state of the art?  Any of
> you found a way to pass on your knowledge?
>

Find someone who’s interested and talk to them?  I mean, that’s kinda what
this list is, right?

The other part: it’s historically been a crap shoot whether the CS
department at any given place came out of EE, in which case it was the
bottom-up here’s a transistor, and here’s a flip-flop, and, look, logic
gates!  Adders!  Et cetera, or it came out of the math department and is a
theory-heavy specialization of some very particular parts of discrete
mathematics and combinatorics.

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

  parent reply	other threads:[~2019-11-15 22:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-12 20:56 [TUHS] Happy birthday Morris worm Norman Wilson
2019-11-12 22:00 ` Dave Horsfall
2019-11-12 22:10 ` [TUHS] buffer overflow (Re: " Bakul Shah
2019-11-12 22:14   ` Larry McVoy
2019-11-12 22:41     ` Robert Clausecker
2019-11-12 22:49       ` Arthur Krewat
2019-11-12 23:45       ` Jon Steinhart
2019-11-13  0:38         ` Warren Toomey
2019-11-13  1:09         ` Arthur Krewat
2019-11-13  0:24       ` Larry McVoy
2019-11-12 22:54   ` Dave Horsfall
2019-11-12 23:22     ` Warner Losh
2019-11-12 23:27       ` Arthur Krewat
     [not found]     ` <alpine.DEB.2.20.1911191443530.10845@grey.csi.cam.ac.uk>
2019-11-21 20:02       ` Dave Horsfall
2019-11-21 20:38         ` Warner Losh
2019-11-21 21:04           ` Clem Cole
2019-11-21 22:06           ` Dave Horsfall
2019-11-21 21:48         ` Steffen Nurpmeso
2019-11-13  7:35 ` [TUHS] " arnold
2019-11-13 18:02   ` [TUHS] Happy birthday Morris worm [ really programming education ] Jon Steinhart
2019-11-13 18:49     ` Tyler Adams
2019-11-13 19:15     ` [TUHS] #defines and enums ron
2019-11-13 21:11       ` Warner Losh
2019-11-13 21:22     ` [TUHS] Happy birthday Morris worm [ really programming education ] Chet Ramey
2019-11-15 22:49     ` Adam Thornton [this message]
2019-11-15 23:59       ` Theodore Y. Ts'o

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=CAP2nic1ysr11mL3WHPf9Tqag2PHaoZUY3gvB9+_W-LDh6yTTKQ@mail.gmail.com \
    --to=athornton@gmail.com \
    --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).