2 ms·
> folks that won’t keep the service running wanting to have a say in our payload wanting us to change This is my single biggest gripe with DevOps. If you’re no
by sgarland 3y ago
> folks that won’t keep the service running wanting to have a say in our payload wanting us to change
This is my single biggest gripe with DevOps. If you’re not going to be fixing it, why on earth do you get a say as to how I build it? It’s nearly _always_ a one-way street, too – when’s the last time Ops successfully ordered Dev to change some specific part of their code (modulo things like, “hey, you really need to add a rate-limiter”)?
- acjohnson55 3y agoIMO, this phenomenon is not specific to DevOps. I've seen this happen when there are official architects or architecture committees. One of the problems about debating DevOps is that there's no single agreed upon meaning. That probably also impedes its success. To me, the essence is that there are engineers whose job it is to give product and service devs the ability to do their own operations through software that simplifies basic shared concerns. That does not mean mandating solutions.