From: Dan Cross <email@example.com>
To: segaloco <firstname.lastname@example.org>
Cc: COFF <email@example.com>
Subject: [TUHS] Re: Generational development [was Re: Re: Early GUI on Linux]
Date: Mon, 27 Feb 2023 16:04:59 -0500 [thread overview]
Message-ID: <CAEoi9W4M9BLLaSGOF9mgYFENq=uDQA0tQiXNd0cEDHb82CsZ0Q@mail.gmail.com> (raw)
[Redirecting to COFF; TUHS to Bcc:]
On Mon, Feb 27, 2023 at 3:46 PM segaloco via TUHS <firstname.lastname@example.org> wrote:
> I see the wisdom in your last line there, I've typed and deleted a response to this email 4 times, each one more convoluted than the last.
> The short of my stance though is, as a younger programmer (29), I am certainly not a fan of these trends that are all too common in my generation. That said, I've set foot in one single softare-related class in my life (highschool Java class) and so I don't really know what is being taught to folks going the traditional routes. All I know from my one abortive semester of college is that I didn't see a whole lot of reliance on individual exploration of concepts in classes, just everyone working to a one-size-fits-all understanding of how to be a good employee in a given subject area. Of course, this is also influenced by my philosophy and biases and such, and only represents 4-5 months of observation, but if my minimal experience with college is to be believed, I have little faith that educational programs are producing much more than meat filters between StackOverflow and <insert code editor here>. No offense to said meat filters, people gotta work, but there is something lost when the constant march of production torpedoes individual creativity. Then again, do big firms want sophisticated engineers or are we too far gone into assembly line programming with no personal connection to any of the products? I'm glad I'm as personally involved in the stuff I work with, I could see myself slipping into the same patterns of apathy if I was a nameless face in a sea of coders on some project I don't even know the legal name of any given day.
This is an extraordinarily complicated subject, and it's really full
of nuance. In general, I think your categorization is unfair.
It sounds like you had a bad experience in your first semester of
college. I can sympathize; I did too.
But a thing to bear in mind is that in the first year, universities
are taking kids (and yes, they are kids...sorry young folks, I don't
mean that as a pejorative, but consider the context! For most young
people this is their first experience living on their own, their first
_real_ taste of freedom, and the first where they're about to be
subject to rigorous academic expectations without a lot of systemic
support) with wildly uneven academic and social backgrounds and
preparing them for advanced study in a particular field...one that
most haven't even identified for themselves yet. For the precocious
student, this will feel stifling; for many others it will be a
struggle. What, perhaps, you see as lack of intellectual curiosity may
have in fact been the outward manifestations of that struggle.
That said...Things are, legitimately, very different today than they
were when Unix was young. The level of complexity has skyrocketed in
every dimension, and things have gotten to the point where hack upon
hack has congealed into a system that's nearly bursting at the seams.
It's honestly amazing that anything works at all.
That said, good things have been invented since 1985, and the way many
of us "grew up" thinking about problems doesn't always apply anymore.
The world changes; c'est la vie.
- Dan C.
> ------- Original Message -------
> On Monday, February 27th, 2023 at 12:22 PM, email@example.com <firstname.lastname@example.org> wrote:
> > Chet Ramey email@example.com wrote:
> > > On 2/27/23 3:04 PM, firstname.lastname@example.org wrote:
> > >
> > > > IMHO the dependence upon IDEs is crippling; they cut & paste to the
> > > > almost total exclusion of the keyboard, including when shell completion
> > > > would be faster.
> > >
> > > Don't forget cargo-culting by pasting shell commands they got from the web
> > > and barely understand, if at all.
> > Yeah, really.
> > I do what I can, but it's a very steep uphill battle, as most
> > don't even understand that they're missing something, or that
> > they could learn it if they wanted to.
> > I think I'll stop ranting before I really get going. :-)
> > Arnold
next prev parent reply other threads:[~2023-02-27 21:05 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 21:31 [TUHS] Early GUI on Linux Paul Ruizendaal
2023-02-25 22:49 ` [TUHS] " Dan Cross
2023-02-26 1:27 ` Larry McVoy
2023-02-26 0:39 ` Warner Losh
2023-02-26 1:14 ` Steffen Nurpmeso
2023-02-26 15:50 ` Leah Neukirchen
2023-02-26 16:13 ` Larry McVoy
2023-02-26 16:23 ` Leah Neukirchen
2023-02-26 16:32 ` Warner Losh
2023-02-26 16:39 ` Will Senn
2023-02-26 19:58 ` Dave Horsfall
2023-02-27 0:16 ` Adam Thornton
2023-02-27 10:09 ` Ralph Corderoy
2023-02-26 2:21 ` Jonathan Gray
2023-02-27 17:22 ` Paul Ruizendaal
2023-02-27 18:32 ` Warner Losh
2023-02-26 2:27 ` Will Senn
2023-02-26 2:30 ` Will Senn
2023-02-26 2:40 ` Theodore Ts'o
2023-02-26 3:28 ` Dan Cross
2023-02-26 3:45 ` Warner Losh
2023-02-26 5:24 ` John Cowan
2023-02-26 5:36 ` Steve Nickolas
2023-02-28 3:35 ` Dave Horsfall
2023-02-27 17:22 ` Paul Ruizendaal via TUHS
2023-02-27 17:59 ` Arno Griffioen via TUHS
2023-02-27 18:07 ` Warner Losh
2023-02-27 20:04 ` [TUHS] Generational development [was Re: Re: Early GUI on Linux] arnold
2023-02-27 20:08 ` [TUHS] " Chet Ramey
2023-02-27 20:22 ` arnold
2023-02-27 20:46 ` segaloco via TUHS
2023-02-27 21:04 ` Dan Cross [this message]
2023-02-28 7:59 ` arnold
2023-02-28 15:28 ` Clem Cole
[not found] ` <CAP2nic1STmWn5YTrnvFbexwwfYWT=pD28gXpVS1CVSfOOwxx7g@mail.gmail.com>
2023-02-28 15:50 ` [TUHS] Fwd: " Adam Thornton
2023-02-27 20:50 ` [TUHS] " Chet Ramey
2023-02-27 20:55 ` Bakul Shah
2023-02-27 21:01 ` segaloco via TUHS
2023-02-27 21:15 ` Chet Ramey
2023-02-27 21:22 ` Dan Cross
2023-02-27 20:30 ` [TUHS] Re: Early GUI on Linux Dan Cross
2023-02-28 1:10 ` Alexis
2023-02-28 1:27 ` Dan Cross
2023-03-01 16:39 ` Paul Ruizendaal
2023-03-01 16:54 ` Larry McVoy
2023-03-01 17:22 ` Paul Ruizendaal
2023-03-01 17:52 ` Larry McVoy
2023-03-02 1:17 ` Jonathan Gray
2023-03-02 4:28 ` Larry McVoy
2023-03-02 6:46 ` [TUHS] X timeline Lars Brinkhoff
2023-03-01 18:59 ` [TUHS] Re: Early GUI on Linux Theodore Ts'o
2023-03-02 7:27 ` arnold
2023-02-28 1:08 ` Jonathan Gray
2023-02-28 1:15 ` Clem Cole
2023-02-27 20:56 ` Will Senn
2023-02-27 22:14 ` Andru Luvisi
2023-02-27 22:31 ` David Arnold
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).