Robert Read, Principal Engineer at a big recruitment company, has written a riveting essay on How to be a programmer, 47 pages of condensed experience and common sense.

The article does not mention Perl, but it explains in detail what technical and personal qualities you should have to be a good programmer.

The first topic mentioned is "Learn to debug."
This entering in the middle is both surprising and revealing, because debugging is, in fact, the art of reading code. And you can't expect to become a good writer if you can't read.
The rest of the article focuses on practical issues, from "how to optimize loops" to "how to deal with organizational chaos."

The article also explains how to build personal and team skills, covering almost anything that is related to a programmer's life.
I find particularly useful the advice on how to build your character as a professional, especially when faced with managerial decision that affect the quality of your work. In such cases, you should fight or be ready to quit. Never accept compromise passively.

I personally think that the only thing missing from the article is some focus on data analysis, which has been a matter of debate in the Monastery before, but on the whole the article makes a great meditation stimulus.

 _  _ _  _  
(_|| | |(_|><
 _|

In reply to Article on how to be a programmer by gmax

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.