Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot

Re: What sets Perl back

by fokat (Deacon)
on Dec 11, 2005 at 19:11 UTC ( #515887=note: print w/replies, xml ) Need Help??

in reply to What sets Perl back

The comment below is not an attack against gunzip but rather a general call for opinions...

I'm afraid I find module errors well over my head and don't think your average Perl developer should have to understand such internals.

Am I the only one that finds this snippet disturbing? Shouldn't an "average <language> developer" understand the environment he/she is working in?

IMNSHO, one of the richest tools at the disposal of the Perl community is, precisely, CPAN. I think an APD should understand how this works and how to use this tool.

Really, I don't mean this to be a rant. I'm just curious about what the rest thinks.

Best regards

-lem, but some call me fokat

Replies are listed 'Best First'.
Re^2: What sets Perl back
by BrowserUk (Pope) on Dec 11, 2005 at 20:02 UTC

    Should an 'average' Perl programmer also have to be a cross-platform (Unix + their platform) C guru; makefile expert; XS wiz; and fully versed in the machinations of ExtUtils::MakeMaker, Test::Harness, et al. ?

    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
      ... guru ... expert ... wiz ... fully versed ...

      Well BrowserUK, I think there's a wide gap between the terms you used and the concept of "understanding the platform" that caused my prior node.

      Perhaps my concept of "average Perl programmer" is not the average:-)

      However, I think that given the typical uses we see for Perl, it does not hurt to understand a little better the context in which your code exists and how is it tied with the rest of the platform.

      Best regards

      -lem, but some call me fokat

        For a lot (the majority) of people, computers are just a means to an end, not an end of themselves. And for a lot of people using Perl to run websites for small businesses, clubs and community ventures, who've progressed beyond what static html can do for them, their use of Perl is just one small part of the long list of tasks that they must turn their hand to, daily or weekly, to meet their overall goals.

        We do not expect a decorator to have a surgeons skills and knowledge because they occasionally use a scalpel to make stenciling templates; nor a taxi driver to have a degree in mechanical engineering because he dips his own oil and tops up the radiator and screen wash. And neither surgeons, nor mechanical engineers need to be either Cordon Bleu chefs or waveguide technologists because they nuke their TV dinners.

        For many people, and if they are not yet in the majority they soon will be, moving from driving their computers with the mouse to going under the hood to install perl and a few CPAN modules is the metaphoric equivalent of dipping the oil and changing the spark plugs on their cars. They are intelligent people perfectly capable of following the step by step instructions in the owners manual. They don't need or want to become certified vehicle maintenance engineers, or computer scientists.

        So the pervasive attutudes that programming should be 'left to the professionals' and that 'if they cannot afford to employ one to do this work, they shouldn't be trying to do it', are divorced from the realities of very small businesses, clubs and community groups. Perl is accessible for the most part to your average non-programmer with a few tuits, but there are several areas around it that when things don't quite go as planned, land you in areas that require not just programming skills and education, but very specific sets of experience that even some of us that have extensive programming experience are lacking.

        In particular, unix skills are not a prerequisite for being either in the industry, nor competent within it. That background and skill set are only one of a number of possible backgrounds you may have. I'd even go as far as saying that it is a minority of those competent people within the industry as a whole that have that background. That doesn't make them less skilled or lesser mortals, just differently skilled.

        There are several areas of the Perl build process that defy my understanding. And I think that there are a good number with much greater, relevant experience that find the Perl executable and module build processes, and especially ExtUtils::MakeMaker to be 'black science'. Even Mr Swern has had some choice comments about the state to which it has evolved--and he is maintaining it!

        So yes. The guys that use Perl and to fulfill a small part of their days activities; or Perl and BioPerl to hack at monster genome sequences as a small part of their job roles; or Perl and a few modules as a small but important part of their SysAdmin or BOFH jobs; and even Human Resource or PR department people that want to pull data from their Excel spreadsheets and munge it a little before incorporating it into their PDFs; are all Perl programmers for some greater or lesser part of their day. And the accumulation of these people into the overall pool of "Perl programmers", does lower the average CS & SE content of the pool.

        In some quarters this is frowned upon as dilution or demeaning to the professional hard core of the pool, but I dispute this. It reflects on the accessability, universality and useability that are the trademarks of Perl; and that as I understand it, Mr Wall fought hard to instill in Perl 5, and continues to fight hard to retain in Perl 6. To my mind, that accessibility is a good part of what makes Perl, and it shouldn't be looked down on by those career professional programmers amongst us who have also found Perl to be a useful tool in our work or play.

        Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
        Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
        "Science is about questioning the status quo. Questioning authority".
        In the absence of evidence, opinion is indistinguishable from prejudice.

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://515887]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others drinking their drinks and smoking their pipes about the Monastery: (4)
As of 2021-11-27 11:34 GMT
Find Nodes?
    Voting Booth?

    No recent polls found