http://www.perlmonks.org?node_id=504824


in reply to Re: I'm all for the type of job posting Skip Huffman made
in thread I'm all for the type of job posting Skip Huffman made

I'm not trying to be contentious, here, but why should it be? I don't think the site has anything as definite as a mission statement (in fact, I sort of hope it doesn't), but if it did, I'd be very surprised to see "nurturing small businesses" anywhere on it. In particular, why is this more relevant to a Perl programming site than, say, any of the dozen or so database-related questions I've seen considered with "deleteónot Perl" as the reason?



If God had meant us to fly, he would *never* have given us the railroads.
    --Michael Flanders

  • Comment on Re^2: I'm all for the type of job posting Skip Huffman made

Replies are listed 'Best First'.
Re^3: I'm all for the type of job posting Skip Huffman made
by dragonchild (Archbishop) on Nov 02, 2005 at 13:58 UTC
    Because of the number of Perl advocacy meditations we seem to be dealing with.

    My criteria for good software:
    1. Does it work?
    2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

      I'm not entirely clear on your point, here. Is there a logical connection between Perl advocacy and small business development that I'm somehow missing?



      If God had meant us to fly, he would *never* have given us the railroads.
          --Michael Flanders

        Advocacy isn't just about shouting from the rooftops. The single greatest piece advocacy that Perl has is the fact that Amazon and CitySearch both run on it, after both evaluated and discarded Java as unable to meet their needs. So, if we have a lot of small businesses choosing to use Perl over some other choice, that is advocacy.

        Java's greatest piece of advocacy is "Everyone else is doing it, so you won't be fired when the project fails." Sun can point to hundreds of mid-size companies that have large Java projects. Java projects have hundreds of developers on them. Hence, you have to keep up with the Joneses. That is advocacy at its finest.

        Since Perl doesn't require dozens of developers on a single project, that's actually seen as a detriment to some PHB's. So, we need to be able to point to succesful ventures like Flying Car Television as startups that succeed basing their infrastructure on Perl. Otherwise, we lose the advocacy war.


        My criteria for good software:
        1. Does it work?
        2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
Re^3: I'm all for the type of job posting Skip Huffman made
by sauoq (Abbot) on Nov 02, 2005 at 17:11 UTC
    In particular, why is this more relevant to a Perl programming site than, say, any of the dozen or so database-related questions I've seen considered with "deleteónot Perl" as the reason?

    I'm sure you asked this question seriously, so I'm wondering what fault you will find in the obvious answer: because the offer was for a Perl programming position. If it had been for a database administrator or an IT manager or a Java programmer, it would have been considered, downvoted, and reaped and if it got any responses at all they would have been rebukes. But, to Perl programmers, information about Perl programming jobs might have value.

    † Emphasis added.

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

      I find fault in the presumption that more of us are unemployed than using Oracle. ;-)

      More seriously, and leaving aside the transient/permanent issue (though I do think it's an important one), I personally find the connection between "solving technical problems encountered while using Perl" and "solving technical problems encountered while using MySQL" to be stronger than the connection between the former and "seeking employment based on my existing Perl knowledge." Obviously, both are stronger than the connection to "seeking employment as a database administrator," but that particular question is not on the table.

      This is somewhat tangential to the point I was trying to make, however, since the antecedent of "this" was not SkipHuffman's post (which I cheerfully ignored until it became a subject of controversy), but rather "nurturing small businesses", which I positted in response to dragonchild's apparent assertion that Perlmonks had an affirmative obligation to encourage entrepreneurship. With which assertion I (as you might guess) disagree.



      If God had meant us to fly, he would *never* have given us the railroads.
          --Michael Flanders

        which I positted in response to dragonchild's apparent assertion that Perlmonks had an affirmative obligation to encourage entrepreneurship. With which assertion I (as you might guess) disagree.

        Okay, well, I agree with you there. I don't think that Perlmonks has any obligation to encourage entrepreneurship.

        I really am thinking a jobs section would be a good idea though. And I'm finding more and more fault with all the arguments against. The transient/permanent issue, for example. All we'd have to do is leave job postings out of search results. (Unless someone is searching specifically for them via Super Search in which case they'd get ordered by newest-first by default.) Most nodes on here are probably never revisited anyway, so the real value of their permanence isn't much... but we keep them anyway. So, I don't see a big deal about keeping more nodes around even if they do have near zero long term value.

        -sauoq
        "My two cents aren't worth a dime.";
        
Re^3: I'm all for the type of job posting Skip Huffman made
by SkipHuffman (Monk) on Nov 02, 2005 at 16:57 UTC

    I agree that "nuturing small business" would be inappropriate. But what about "encouraging professional opportunities for Perl users"?

    Skip