Thus, I guess I'm saying I don't see a need or a desire for similar types of postings at perlmonks (just my opinion).

I think the desire is there among at least some of us. Let's talk about the need.

I think it depends somewhat on whose perspective you are looking at it from. I guess the entreprenueurs could go somewhere else. Maybe they could even find such a concentrated pool of capable Perl programmers elsewhere... (doubt it though.)

But, how about us? What other board would give us the same sort of review and insightful commentary such offers would get from other monks here? That's one thing that the standard answer (jobs.perl.org) doesn't address. There's no one there asking the questions you wish you had thought of or catching the red flag that you missed. That's something PM could provide that you don't find elsewhere. (At least, not that I know of.)

I've thought about this quite a bit since a CB discussion the other day. I was swaying toward the idea of creating a jobs section when bart mentioned the same issue GrandFather did and that was enough to convince me it wasn't right for the monastery. At least temporarily. I'm not so sure again. I'm not even so sure that the nodes have to be temporary. I mean... how many are there going to be? Why not keep them around as history? Theoretically, it might not seem like such a hot idea, but I really don't see much of a practical downside.

In that same discussion, tye noted his concern about spam. He asked whether I thought the job posts would all be for Perl jobs. And he voiced concern about too many PM resources being diverted to such a section. I don't buy those arguments though. I think the current moderation system would keep the jobs posted on "topic" so to speak. We could even, if we saw fit, institute a system whereby only monks of, say, level 5 could post a job. Yes, the moderation system should be counted as a monastery "resource" but, it's one we have plenty of to go around. It's not like we can only consider some number of nodes a day based on our XP and we aren't limited on how many considerations we vote on either. Bad job posts would fail to be approved in the first place and then they'd be taken care of efficiently and in short order. I just can't see how it would be otherwise.

So, I've swung back to the other side again and I find each time I get over here to this side of the fence, it is more and more likely that this will be where I will finally rest my opinion on the issue. Done well, I think a job posting section would be very worthwhile.

-sauoq
"My two cents aren't worth a dime.";

In reply to Re^2: I'm all for the type of job posting Skip Huffman made by sauoq
in thread I'm all for the type of job posting Skip Huffman made by metaperl

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.