Earlier quoted context omitted.
The big difference here is that CI/CD should ideally be taking away annoying work from devs so that they can more smoothly go from problem/feature -> hard thinking work -> code -> out the door, without having to deal with the highly repetitive part of the job. The problem is that there's an expectation that this increase team velocity more than it increases quality of living. 15 years ago in IT if you could automate…
> The big difference here is that CI/CD should ideally be taking away annoying True. OTOH, I feel like some version of this is always sold as the worker-facing rationale for automation and increased productivity. For some jobs, it's "hey, we're going to automate your job away so you can go do something meaningful with your life". For devs, it's "we're going to automate this for you so you can focus on meaningful work…
I dont disagree with your observations, just saying "productivity" gain is pretty far down the list of benefits to me personally