Re: Hiring Perl Talent, Hiring Perl Monks

Hire people who come with recommendations from people who you trust or have a well-known good reputation in the community.

Give people you haven't personally worked with small tasks before you give them big tasks.

Supervise the work so you don't get to the end and realize it's all crap you don't want. I'm not against off-shoring work, but if you can't talk to the developers, you're setting yourself up for failure.

Don't hire primarily based on price. Lowest bidders usually make you end up hiring someone else anyway.

--
brian d foy <brian@stonehenge.com>

Comment on Re: Hiring Perl Talent, Hiring Perl Monks

Replies are listed 'Best First'.
Re^2: Hiring Perl Talent, Hiring Perl Monks by cbrandtbuffalo (Deacon) on May 03, 2005 at 11:57 UTC
I agree with brian. It will require some good project management on your part, but if you have a good design you should be able to break off some smaller tasks and give them to prospectives on a trial basis. Spec the tasks out fully and make it clear what you want. For example, code it and provide tests to demonstrate it works. You didn't mention whether it was hourly or piece-work. If hourly, you get a feel for how much time it took them when they report back. Piece-work is where you set an estimated hour value or dollar value for a feature and the coder does the work for that amount. This can be tough when estimating, and you may need to be prepared to be fair if a task ends up being bigger than expected. Having many smaller, defined tasks also allows you to pursue a few coders. If one or two don't work out, you still have some people working. When you get to the final integration, which can be the tough part, you'll know who you are getting the best work from. Also, if you know what frameworks you are going to use to build it (what modules) that can help. Sometimes the module authors themselves are contractors, so you can literally get the expert in a particular module or technology working on your project. This has the advantage that they can add features to their module if you really need them.	[reply]

Replies are listed 'Best First'.

Re^2: Hiring Perl Talent, Hiring Perl Monks
by cbrandtbuffalo (Deacon) on May 03, 2005 at 11:57 UTC

You didn't mention whether it was hourly or piece-work. If hourly, you get a feel for how much time it took them when they report back. Piece-work is where you set an estimated hour value or dollar value for a feature and the coder does the work for that amount. This can be tough when estimating, and you may need to be prepared to be fair if a task ends up being bigger than expected.

Having many smaller, defined tasks also allows you to pursue a few coders. If one or two don't work out, you still have some people working. When you get to the final integration, which can be the tough part, you'll know who you are getting the best work from.

Also, if you know what frameworks you are going to use to build it (what modules) that can help. Sometimes the module authors themselves are contractors, so you can literally get the expert in a particular module or technology working on your project. This has the advantage that they can add features to their module if you really need them.

[reply]