These nodes are becoming painful. Here's the new Faq:

Q: How can I become a better Perl programmer

A: Become a better programmer by learning the language independent essentials (ie compsci stuff - yes, this is required. No, you don't have to go to university). Write pseudo-code (aka Python) to enforce the principles. After you've done that read through Programming Perl 3rd edition (don't bitch, the book's the best there is out there). Then apply the principles by writing clean, modular code. If you don't get something, do search or RTFM.

Q: What code should I write to start with?

A: Something that sounds interesting. If nothing sounds interesting then flip a coin. If you don't like the results pick anything else. If you still can't decide, go study sociology, there's enough half-assed programmers out there already.

Q: Should I write one-liners?

A: No, write real-world code. One liners are for people who don't know what the word "maintenance" means. Write real-world, reusable code.

Q: How can I learn to write code for big, important projects?

A: Think of what's an important gap that is currently not filled by free software. Write clean, modular code with well thought out interfaces. Proceed to build upon it until it meets your definition of "big." If in doubt, download and read (yes, read) the source for existing free software projects. Do not assume their code is good.

Q: What license should I release my code under?

A: The GPL. It is solid, relatively tested, and will ensure your code remains free. Chances are you won't make any money off selling your software commercially (especially if you asked this question). Financially you're probably better off distributing your software for free and selling support for it. Others will also be more willing to offer advice, patches, and publicity for your project.

That's all the major questions I can think of for now. If I missed any let me know.

You can know the name of a bird in all the languages of the world, but when you're finished, you'll know absolutely nothing whatever about the bird... So let's look at the bird and see what it's doing -- that's what counts. I learned very early the difference between knowing the name of something and knowing something. - Richard Feynman.

In reply to Re: Where does one get experience? by Anonymous Monk
in thread Where does one get experience? by UberGeek27

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.