I posted a similar question recently and got great answers! My problem with coding is
that the learning process seems mysterious at times. I guess I'm used to a cut and
dried approach to things and learning to code isn't, or am I wrong? For example,
sometimes I'm not sure which books to read or in what order or what source code to
study or how to study or how good you have to get before you can get a job coding or
how to get good at coding, etc., etc. Whenever I speak to aspiring coders they express
similar concerns and questions. Is there any info (general advice, life experiences,
sites, FAQ's, etc.) about the process of learning to program? Thanks!
-----Original Message-----
From: drieux [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 29, 2002 11:27 AM
To: [EMAIL PROTECTED]
Subject: Re: Selftuition
On Monday, April 29, 2002, at 06:00 , Richard Adams wrote:
[..]
> The main problem I've had learning Perl is trying to separate out
the
> "need
> -to -know" stuff from the "very clever but you can get by without
it"
> info,
> esp in the manpages and the Camel book. Also I find the exercises in
the
> deitel book for C very useful for getting the syntax firmly learned.
[..]
My complements to the rest who have proposed very useful bits.
What I would advocate are two areas of importance - the first
is the simplest:
perldoc perl
and understand the sections already documented with the perl
code that you are privy to at this point - since this material
is online and faster to get at than the 'books'. This will also
prep you to read about new modules as you run into them, and
before the luddites have the chance to muder treePersons to
see you what you could have read on line... 8-)
The second most important notion is
use Benchmark;
http://www.wetware.com/drieux/CS/lang/Perl/Beginners/BenchMarks/
If you really want a clue about the trade offs of this or that,
go and Benchmark it - resolve the technical distinctions yourself -
the failure of both C and perl is that they do not prevent you
from doing that which you wish....
It is a rather fun way to resolve why you want X over Y as a solution.
After this you can get into the developer suite of tools and
since you are coming from the K&R 'C' side you will of course
want to better understand h2xs - so that you can get into the
whole process of creating your own 'just a stack of functionality'
perl modules - so that you can 'reuse code' - without having to
get lost in the maze of OO stuff.....
http://www.wetware.com/drieux/CS/lang/Perl/PM/
Along the way, use the beginner's mailing list as the
"play along at home game."
If you see a neat piece tossed up as a 'solution' or a 'problem'
prove it to yourself....
and last but not least,
did we mention '-w' and 'use strict;'
YES, just do it.
ciao
drieux
---
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
