Re: A corrolary to TMTOWTDI

I have been programming perl for a while: seriously in the last year and sporatically before that. I often find here on Perlmonks some reference to a CPAN module that would have helped me at one stage of some project or another. Some are recent additions to the repository (e.g Text::xSV and Tie::Cycle) while some did not turn up with searches I made.

One problem is that in the heat of programming, one does not often see how to generalize one's problem and then describe it in a way a CPAN search can find it.

Finally, it was a great pleasure when I found CPAN.pm. It was not installed by default on my systems. Maybe one way to help promote the use of CPAN is to get more installations to include CPAN.pm by default.

Comment on Re: A corrolary to TMTOWTDI Select or Download Code

Replies are listed 'Best First'.
Re: Re: A corrolary to TMTOWTDI by da (Friar) on Jun 01, 2001 at 18:14 UTC
One problem is that in the heat of programming, one does not often see how to generalize one's problem and then describe it in a way a CPAN search can find it. Yup, this is precisely where perlmonks shines. Not only will people re-describe your problem for you, they will give you answers too. So here's the problem as I see it: CPAN seems mostly useful if I know exactly what I'm looking for. Perlmonks is a great resource but people can take advantage of the monks. The perlmonk search sometimes rocks, but sometimes it's really frustrating, again if you don't know what you're looking for. Possible solutions: Starting from CPAN. The WAIT search is good to narrow down your search terms; it indexes module POD files and does OK on many-word searches. But WAIT is somewhat slow and the results are one-line links so you need to do some more digging in each result to find your search terms. Starting from google. Doing a google search restricted to site:perldocs.com works as well, and perhaps better. perldocs.com indexes POD files and other perl documentation, and has two lines of context for each result, which is very useful. The higher-ranked results are usually close to what I was looking for. Ultimately what I'd love to see is an integrated CPAN/perlmonks search, where search terms are weighted like google's, and results from perlmonks are also weighted by their reputation. `___` `-DA`	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re: Re: A corrolary to TMTOWTDI
by da (Friar) on Jun 01, 2001 at 18:14 UTC

One problem is that in the heat of programming, one does not often see how to generalize one's problem and then describe it in a way a CPAN search can find it.

Yup, this is precisely where perlmonks shines. Not only will people re-describe your problem for you, they will give you answers too.

So here's the problem as I see it: CPAN seems mostly useful if I know exactly what I'm looking for. Perlmonks is a great resource but people can take advantage of the monks. The perlmonk search sometimes rocks, but sometimes it's really frustrating, again if you don't know what you're looking for.

Possible solutions:

Starting from CPAN. The WAIT search is good to narrow down your search terms; it indexes module POD files and does OK on many-word searches. But WAIT is somewhat slow and the results are one-line links so you need to do some more digging in each result to find your search terms.

Starting from google. Doing a google search restricted to site:perldocs.com works as well, and perhaps better. perldocs.com indexes POD files and other perl documentation, and has two lines of context for each result, which is very useful. The higher-ranked results are usually close to what I was looking for.

Ultimately what I'd love to see is an integrated CPAN/perlmonks search, where search terms are weighted like google's, and results from perlmonks are also weighted by their reputation.

___
-DA

[reply]
[d/l]
[select]