Tom Metro wrote:Adam Turoff <[EMAIL PROTECTED]> wrote:
If Perl per se matters to you that much, then you should find some way to make it your day job.
Hmmm...isn't that sort of what were talking about? If there's no job market for Perl, that's kinda hard to do. Even if you run a business where Perl is embedded, there are challenges to using it if the marketplace shows resistance to it.
There are businesses and products that are built on Perl where the implementation language is not a concern. RT and Bricolage come to mind.
I'd be willing to bet that Jesse has encountered, with some regularity, resistance to commercial adoption of RT due to its use of Perl.
This isn't a black-and-white situation. There are anecdotal failures and successes on both sides. (Movable Type is an example of another success. There are a bunch of them.)
What it comes down to is a personal opinion or personal judgment of how the market is behaving and which direction it is going in (unless one of us cares to dig up and cite statistics). All I can do is draw from my past experience working at an actual company selling a pure Perl product, and conjecture that there is increasing resistance to adopting a Perl-based product as you move into higher-end markets.
Another model is focusing on service, rather than the deliverable.
Absolutely. This is what I was getting at in my original post when I referred to "solutions oriented consulting." The objective is to accomplish something for the customer, and the details of the implementation are less relevant.
I'm expecting that to be quite true for certain types of customers and certain sizes of companies. I'd also expect implementation details to become more significant in many cases as you move on to larger customers where the customers have their own in-house development staff and infrastructure that you need to integrate with.
Focusing on the small job market for Perl is a red herring. ...
It isn't. And for the same reason that a glib comment posted to the list saying that most jobs in *any* field are entry level, in response to my comment that most available Perl jobs are entry level.
Your point about the greater efficiencies of Perl programmers is valid (though I suspect rarely accepted by the IT industry), but what I'm comparing is not the quantity of Perl jobs vs. say Java jobs, but what the market looks like specifically from my perspective, as a senior Perl developer in MA.
Obviously there are going to be fewer jobs after the bubble burst, but it seems there are fewer (or about the same) now than there were in 2002. And as the rest of the market recovers, it's having a more muted effect on the Perl job market. To me, that's a symptom of an underlying market shift.
-Tom
_______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
