[johntdaly]

I think those numbers are probably based on source code contributions. I can believe those statistics, what is missing is the why.

Some people just aren’t good programmers. I knew some of those, one turned out to be great at testing instead. Junior programmers, new programmers (to the project/company or language or field) are slow and they might get better. Then you have burnout. There was a story here about a guy that didn’t contribute much because he mentored and pair programmed and did other tasks to make the life of other programmers easy.

There are a lot of good reasons so before you go optimizing on numbers, check the why.

[shagie]

> those numbers are probably based on source code contributions

The other part of that is a "more senior developers tend to do things outside of things seen with git commit." Meetings, commenting on code reviews, and documentation are the first three "not tracked in git" that come to mind.

Other things like proof of concepts may not find their way to the actual project repos (and thus has little visibility in the report).

That said, there are certainly developers who are at the 0.1x median even when they spend their full time working on solving that problem. They just work really slowly.