Re:Scaling and Developer Productivity (2016)
by pgroves on Tuesday June 09, 2020 @09:46AM
(#23466583)
The same code split across two pull requests is preferable to the rest of the team (assuming they are actually trying to understand the PRs). Sort of a clever way to incentivize that.
[ Parent
| on HN ]
Re:Scaling and Developer Productivity (2016)
by JamesSwift on Tuesday June 09, 2020 @12:48PM
(#23468248)
I'd argue its a way to _hopefully_ incentivize that. Number of deploys has no inherent value though, so optimizing it opens you up to pointless progress.
How about, instead, you optimize _time to deploy_. i.e. the delta between code submitted for review and code running in production. Then, who cares if we didn't deploy 5 times today. Maybe we didn't have 5 things that needed updated.