4 ms·
>> If the application is so simple that you can get actual productivity in someone in the first couple hours then stop trying to hire candidates and outsource t
by Nursie 13y ago
>> If the application is so simple that you can get actual productivity in someone in the first couple hours then stop trying to hire candidates and outsource the entire thing to India for a fraction of the cost.
Pretty much this. For some large, complex codebases I've worked on the metric has been that if the engineer can meaningfully contribute within a week then they're likely damn good at the job. Two weeks and they're still fine.
- Tyrannosaurs 13y agoIf you take the time others need to spend with them getting them up to speed away, I generally consider it good if they break even in the first month.
- codeonfire 13y agoThat's a very one-sided metric. There is a large range of definitions of large and complex. The dev process or team size might make it extremely difficult for outsiders to contribute. I can understand why you and others would like to attribute all productivity squarely on skill. In almost all cases, everyone is trying to manipulate the consensus of who's productive and who's not, who made a good hire, who has good employees, etc.
- alandarev 13y agoIt might as well signal of an over-complexed project design.
- Nursie 13y agoSome systems are needfully complex, because they do a hell of a lot. And some are needlessly complex but you inherited them from another, long-gone team and somebody has to maintain, improve and update them, unfortunately!