9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Sam <sah@softcardsystems.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Old Pharts Reminiscing?
Date: Mon, 17 Nov 2003 08:46:31 -0500	[thread overview]
Message-ID: <Pine.LNX.4.30.0311170821420.27514-100000@athena> (raw)
In-Reply-To: <2147483647.1069015526@[192.168.42.6]>

> > More to the point, I'm not sure it's possible.  People aren't
> > interested in learning how to program elegantly
>
> I don't agree. The people who want to, or like to, learn will have this
> interest. But most of the people getting into software these days
> aren't interested in programming, engineering, or even learning for
> that matter. It's all about padding your resume.

I'm not so sure it's necessarily the new programmer's fault.
I went through school without a single utterance on the topic.
The person responsible for teaching introductory programming gave
higher scores to those individuals who littered their code with comments.

"Comments and whitespace make code easy to read, so use lots of them."

There were a few good programmers in the department, but they taught
advanced courses.  By the time the classes came up most people were lost
and resorting to lifting implementations from the 'net for the grade --
as a group, even.  I happened to get lucky and find a mentor after
graduation who sat a stack of books on my desk to set me straight.

I'm exceedingly convinced that's the way to learn coding -- instruction in
the fundamentals combined with application from someone in the trade.
It's a pity the latter isn't more prevalent in education since the
combination of history and craftsmanship can make all the difference.

'Course, I'm still learning my history. :)

Sam



  parent reply	other threads:[~2003-11-17 13:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-17  3:45 Lyndon Nerenberg
2003-11-17  4:02 ` boyd, rounin
2003-11-17 13:46 ` Sam [this message]
2003-11-17 18:10 ` Dan Cross

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=Pine.LNX.4.30.0311170821420.27514-100000@athena \
    --to=sah@softcardsystems.com \
    --cc=9fans@cse.psu.edu \
    /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).