That's why I phrased it "...discussing the work or business side of being a Perl coder...", with the (apparently botched) intention of including all Perl coders' work experiences. "I don't get no respect", "How's the Perl coder job market?", "Problems communicating with non-Perlers", "Useful contract clauses", "The issue of PM postings ownership" (did this ever get resolved?), "Pitching Perl to prospects", "How to find businesses/employers that use Perl".....

After all, although Perl does have its own innate value that transcends life, most of us are Perl coding to earn a living.

But, more interesting - I would be sincerely interested to read more on "tax-dodging slimeballs contractors". Don't worry, the odds of you hurting my feelings are slim to nil. I'm honestly interested in learning more about why some poeple out there might have this opinion of contractors.

---

In reply to Re^3: Any interest / use in a Perl-Work section? by punch_card_don
in thread Any interest / use in a Perl-Work section? by punch_card_don

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

---

• 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.