Just another Perl shrine | |
PerlMonks |
Re: PerlMonks is not a place to go for free codeby Acolyte (Hermit) |
on Jan 22, 2003 at 02:03 UTC ( [id://228914]=note: print w/replies, xml ) | Need Help?? |
There have been several posts on the site recently regarding the merits, or lack thereof, of adding a "code for hire" area to the site. From what I have seen, the concept has recieved mixed reviews with some very solid discussions around the issues of responsibility, liability, etc. You seem to fall clearly in the camp against providing that type of assistance. I concur, but not primarily for the reasons you may think. I think the key to helping people understand what PerlMonks is all about is to explain to them that we are a community that provides developer-to-developer help. This is a place for Perl coders to come learn and get assistance with coding issues. While there may be some generous souls here willing to help out, developer-to-business support ( hereafter "d2b") is not our goal. Developer education is. For that reason, I think d2b solutions would be more appropriate on another site. So what about the people that do come here seeking d2b help? "...I wonder that maybe it would be an improvement if it was declared on the frontpage or another place often seen, that perlmonks is a community, not a place where people can come and demand that we supply free code." What worries me about your proposal is that:
Does anyone else find it annoying that people who want free code use a search engine with a couple of keywords and find this site and assume that we write complete programs for free? Search engines are there for a reason: finding things. They are only as good as the search data entered by the seeker. Since PerlMonks is a key site within the Perl community, chances are that someone with d2b interests is going to run across it, and may make some assumptions as to the purpose of the site. Rather than burying the site under fine print to try to discourage d2b inquiries, why not do what we do for everyone else that comes into the site: welcome them, refer them to our introductory nodes (i.e. Guide to the Monastery and Perl Monks Site FAQ) and then direct them to the appropriate resources such as http://jobs.perl.org/. And as for posting a reply to his post or /msg'ing him, I'd rather not. If he's here to be a part of the site, then he'll come across this post himself :) Noticing that a new user's node has been blown away, and then not providing an explanation when the opportunity arises is just bad community relations, even/especially if it is a business. Why give them the cold shoulder? They may eventually decide that a solution is worth paying for, but after the chilly reception they may dismiss Perl and turn to something like (shudder) Visual Basic. Think of your fellow Perl developers. :) "(Good community relations" eq "more Perl jobs")||(Good community relations" ne "fewer Perl jobs); # take your pickAcolyte Studying at the feet of the masters
In Section
Perl Monks Discussion
|
|