Interesting trend, but for me the critical point is that of the last full paragraph: are we merely creating more work (friction) down stream of the excitable new dev sailing past 10 PRs, and overloading the wizened Senior that's supposed to be able to Quality Check, in a valuable way, each one
This observation is correct -- but to be clear these are in fact merged PRs, so they've made it past the quality gates and reviews and have been merged into production.
"...but it does not, on its own, tell us about the quality of those changes, the amount of rework they generate, or the depth of understanding new hires have of the systems they’re touching."
Having made fun of this I must say that I made a pretty large update to a project I use using codex, in go (which I have never developed in) and it works well, was reviewed well and was accepted by the maintainer of the project. So yeah, there is definitely a boost.
Interesting trend, but for me the critical point is that of the last full paragraph: are we merely creating more work (friction) down stream of the excitable new dev sailing past 10 PRs, and overloading the wizened Senior that's supposed to be able to Quality Check, in a valuable way, each one
This observation is correct -- but to be clear these are in fact merged PRs, so they've made it past the quality gates and reviews and have been merged into production.
My mistake … I still have to wonder, though, were the “quality gate” personas able to adequately apply quality as the PRs came crashing through 🙂
"...but it does not, on its own, tell us about the quality of those changes, the amount of rework they generate, or the depth of understanding new hires have of the systems they’re touching."
was gonna say :)
Having made fun of this I must say that I made a pretty large update to a project I use using codex, in go (which I have never developed in) and it works well, was reviewed well and was accepted by the maintainer of the project. So yeah, there is definitely a boost.