Hacker News new | ask | show | jobs
by bearjaws 1966 days ago
In my professional experience, country really doesn't matter.

What we found to be most effective is clear cut punishments for poor code quality.

We have a itemized list of issues that if we find, the contract would be penalized in points.

Items like OWASP Top 10 count as '10 points' and items like abusing null types are 3 points.

If the contractors exceed more than 15 points of issues in a month we get reimbursed a percentage of the contract. If they exceed (contractMonths * 20 points) worth of issues then the contract is cancelled. Having the 'eject button' is something we've recently added and not had to use yet, thankfully.

Combining this with interviewing the contractors before the work begins has helped reduce defects and having to refactor the code that is build by them.

Overall contractors are a massive time sink, our benchmarks indicate you will need 3 FTEs per 8 contractors to coordinate everything and review the work that has been completed. The quality is usually not the same no matter how much you try.

1 comments

Wow, smart approach! I can tell you that one of our clients recently hired an external tech consultant to evaluate the code and make sure it is done right. I guess it is a good approach too.