News for hackers. Stuff that matters.
Re:I deploy, therefore I am by dvnguyen on Thursday May 14, 2020 @09:26PM (#23187816)
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.

Re:I deploy, therefore I am by StavrosK on Thursday May 14, 2020 @10:04PM (#23188074)
Re:I deploy, therefore I am by xtony on Thursday May 14, 2020 @10:04PM (#23188068)
To 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.
Re:I deploy, therefore I am by pietrovismara on Friday May 15, 2020 @06:49AM (#23190715)
Points 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.
Re:I deploy, therefore I am by Cthulhu_ on Friday May 15, 2020 @05:16AM (#23190303)
I see it as just one part of the story tbh, a deployment itself means nothing.