3 ms·
The hardest part is objectively measuring developer productivity, and if you can find a way to do that where half the community doesn't disagree with you you'll
by pc86 8y ago
The hardest part is objectively measuring developer productivity, and if you can find a way to do that where half the community doesn't disagree with you you'll probably make a lot of money consulting and giving presentations.
- amelius 8y agoYou can make 5 parallel teams work on the same project, then see which one finishes first, or something like that. It might seem expensive, but if it helps to find the optimal working strategy, then for a large company it could be a bargain.
- pc86 8y agoYou'd need to do it on enough projects to move folks around to different teams, and you'd need to do it for long enough on each project to average out the effects of everything from interpersonal differences to Mark going through a divorce, and hope that everyone is employed there long enough not to invalidate huge pieces of your data.
- tdumitrescu 8y agoTo the point of the parent, IMO speed of project execution is often an absolutely terrible metric to optimize for, especially if the parallel teams know that that's the goal. If you can find a generalizable objective metric that works across many different dev projects, then you've found something magical.