I think that our quickness to point out module solutions has several explanations:

• Often, someone is asking "how can I do something". We know that the most expedient way is to use something that's already written.
• Even if the question is really "how is something done" instead, modules can be good to point to. I don't know about you, but I've learned a lot from reading the code of the Perl modules. I don't generally use a module until after I've looked through it; why miss a chance to learn? Besides, I've found un/under-documented (or broken) bits of various modules in this way.
• There is a place in the Perl community for the cut'n'pasters. It may be surprising for you or me, but some people don't really want to be programmers; they're just focused on getting their jobs done. For these people, a simple cookbook solution is a good place to start.
• Even if you're using modules, you still have to know some Perl to glue them together.
• The next generation of gurus will not be the ones who are cutting'n'pasting. They will be (as they are now) the ones who dig into the solutions and the possibilities of the langage and the great work that others have done.