What I meant to say, was what's the next important thing to learn after you have grasped the basics.
I recommend:
- perldoc perlfunc -- memorize function names, and roughly what they do
- perldoc -f <function> -- memorize the usage of this command. It will give you the details on a function, without having to search through perlfunc for it. This assumes you can remember the function name (see step 1).
- If you haven't already, read about good programming style for block structured programming (in any language). Discipline yourself in good practice. Learn how to break huge functions down into managable functions, learn to document your functions as you write them, learn to take the time to choose good variable names. Teach yourself to code for maintainability.
- Read books on testing, and specifically, how to write programs that are easy to test. Programs that are clearly correct are easier to maintain than programs where even the original programmer got confused about what's going on...
- Once you can write good programs, learn to write good perl programs. Master perl idioms, learn what they mean, and what the tradeoffs of using each one are. Learn regular expressions, how to use them, how not to use them, and when to document them (ie. always)
- Learn what CPAN modules are out there: this is not a static task. Learn perl XS if you like. Learn about closures, symbol table manipulations, and start filling in the corners of your perl knowledge.
- Learn everything. If you succeed, tell me how. :-)
--
AC
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
|