measuring programmer productivity is notoriously difficult. Does james, who shipped 20 features without testing thoroughly provide more value? or does joe, who patched a security hole in that time and avoided disaster? what about jason, who facilitated communication between them, and kept the infra going so their changes could go into prod without issues?
It’s clearly Jason in this scenario
We won't be programmers in this scenario.
The results will hopefully be a lot more tangible.