4 ms·
When number of deployments becomes an evaluation metrics, I can imagine an engineering culture like this: - Dev rushes to make merge requests with the cost of
by dvnguyen 6y ago
When number of deployments becomes an evaluation metrics, I can imagine an engineering culture like this:
- Dev rushes to make merge requests with the cost of thoughtful design and testing.
- Tension around code review turnaround time: how dare you take hours to review my code when I'm far behind in the leader board.
- Deployment has a bug? Awesome, now I'll have 2 deployments.
- Deploy faster and break everything.
Frequent and continuous deployment is good. Making it a metrics is bad.
- xtony 6y agoTo be fair, the scoreboard in the post displays the success of the deploys too, which would address the third and fourth point. But of course, people can still game the metric with a ton of insignificant incremental changes that don't do anything.
- StavrosK 6y agohttps://en.wikipedia.org/wiki/Goodhart%27s_law https://en.wikipedia.org/wiki/Goodhart%27s_law
- Cthulhu_ 6y agoI see it as just one part of the story tbh, a deployment itself means nothing.
- pietrovismara 6y agoPoints 1, 2, 4 happen also when you have a deadline culture. It's almost like having a culture that rushes people to results will always compromise on quality.