- Sometimes it takes self-confidence to keep you going on the code, since the aim might seem a bit too high, but as Jeff says, too much will kill you uhm spoil it :) The difference between commercial projects and personal projects (or non-commercial if you will) has a great deal to do with expectations. Altho the users will always want more, on personal projects you have complete freedom (well, uhm usually :) )
- IT = learn ad infinitum. There are always new things to learn, always unknown territory. Take small steps. Don't aim TOO high. Learning the hard way, is the best way. Don't be afraid to roll your own code (I might get --'ed for saying this :) ) , but look at alternatives as well. Don't take things for granted. Read the perlstyle.
- You won't learn a thing if you don't look into the code you copy/paste. You might learn what something does, but not why it does so. Look up the functions you use in the perlfunc, look at how other people use the functions but don't follow it blindly.
Greetz
Beatnik
... Quidquid perl dictum sit, altum viditur.
-
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.
|