MESSAGE
| DATE | 2006-06-08 |
| FROM | Ruben Safir
|
| SUBJECT | Re: [NYLXS - HANGOUT] Re: [nylug-talk] PIG in new york?
|
From owner-hangout-at-mrbrklyn.com Thu Jun 8 23:43:18 2006
Received: from www2.mrbrklyn.com (localhost [127.0.0.1])
by www2.mrbrklyn.com (8.13.1/8.13.1/SuSE Linux 0.7) with ESMTP id k593hGGL009864
for ; Thu, 8 Jun 2006 23:43:18 -0400
Received: (from majordomo-at-localhost)
by www2.mrbrklyn.com (8.13.1/8.13.1/Submit) id k593hGxx009863
for hangout-outgoings; Thu, 8 Jun 2006 23:43:16 -0400
X-Authentication-Warning: www2.mrbrklyn.com: majordomo set sender to owner-hangout-at-nylxs.com using -f
Received: from flatbush.mrbrklyn.com (flatbush.mrbrklyn.com [10.0.0.62])
by www2.mrbrklyn.com (8.13.1/8.13.1/SuSE Linux 0.7) with ESMTP id k593h0in009858;
Thu, 8 Jun 2006 23:43:06 -0400
Subject: Re: [NYLXS - HANGOUT] Re: [nylug-talk] PIG in new york?
From: Ruben Safir
To: NYLUG Technical Discussion
In-Reply-To: <4486B7F6.9070906-at-sccs.swarthmore.edu>
References: <448459CF.1010002-at-sccs.swarthmore.edu>
<20060606111851.GA7016-at-www2.mrbrklyn.com>
<200606060935.17323.phantom21-at-mindspring.com>
<20060606231214.GA11331-at-www2.mrbrklyn.com>
<20060607021519.GB27804-at-lenin.net>
<20060607022533.GA12534-at-www2.mrbrklyn.com>
<448643DA.4070009-at-sccs.swarthmore.edu> <20060607040048.GU22904-at-ayvali.org>
<20060607040816.GF27804-at-lenin.net>
<20060607040940.GB13523-at-www2.mrbrklyn.com>
<4486B7A7.5000207-at-sccs.swarthmore.edu>
<4486B7F6.9070906-at-sccs.swarthmore.edu>
Content-Type: text/plain
Date: Thu, 08 Jun 2006 23:44:29 -0400
Message-Id: <1149824670.23185.42.camel-at-flatbush.mrbrklyn.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.1
Content-Transfer-Encoding: 7bit
Sender: owner-hangout-at-mrbrklyn.com
Precedence: bulk
X-Keywords:
X-UID: 11170
Status: RO
Content-Length: 2415
Lines: 51
> Another quick idea -- if we're not satisfied with what we find out
> there, we can always write our own, either as a standalone book or as a
> HOWTO at TLDP.
>
There are advantages of writing your own. I gave this some thought
today. One of the reasons I wrote my own Perl text was because the
other works didn't address the needs I had as a teacher. There was too
many cook books, too many short cuts, not a clear enough explanation of
proper programming technique, how Perl fit into the entire programming
environment, the ecosystem of Free Software and general computing. I
wanted to give the student the ability to evaluate pros and cons, not
just of Perl, but also other languages. I needed them to understand
memory is managed in a general sense. There is just so much slop on a
stick among programmers. I wanted my programmers to give serious
consideration of software architecture.
The result was, IMO, the best programming class that had been available,
not just Perl. The work was based on years of serious training of
programmers and it was the students who gave the program its biggest
praise. At the end of the program, they could do things they had never
thought they could do before. They had deep and lasting understanding
of coding, Perl, and computers.
I often taught returning house wives in continuing education, and the
program and text are largely designed as such. But to my surprise, the
guys who got some of the most out of the approach were the serious
engineers and scientists who were forced to actually view the language
on a basic level of bits and bytes, and then built up their
understanding from there.
Since I largely became a professional programmer as a result of my
coding when I went for my PhD in Physical Chemistry, I suppose I took a
very math or science textbook like approach which resonated with other
serious engineers. There are a lot more decent general chem books than
beginning programming texts. I wanted to bridge that gap.
The resulting work was worthwhile and unique.
Ruben
> dsc
> _____________________________________________________________________________
> Hire expert Linux talent by posting jobs here :: http://jobs.nylug.org
> The nylug-talk mailing list is at nylug-talk-at-nylug.org
> The list archive is at http://nylug.org/pipermail/nylug-talk
> To subscribe or unsubscribe: http://nylug.org/mailman/listinfo/nylug-talk
|
|
