4 ms·

A bad devops team becomes what I call "dev obs" which is short for a phrase I made up, developer obstructions. I use this to describe devops teams that have for

A bad devops team becomes what I call "dev obs" which is short for a phrase I made up, developer obstructions. I use this to describe devops teams that have forgotten (or maybe never knew) their primary purpose and instead do their own thing independent of the developers and business they are supposed to be supporting. This can include: Upgrading, replacing, deprecating, turning off key parts of infrastructure without any notice or warning "Scheduled" changes to systems that are scheduled nowhere but their own minds and then become angry when this is pointed out Turning off logging because "it's expensive to store logs" (get a better logging system then) totally ignoring the huge costs of production failing with no visibility as to why Enforcing their own ideas of unit test coverage and the like without speaking to the developers, as if they know more about it than the developers Enforcing package management security in a way that simply isn't compatible with a particular language's tooling leading to the scenario that all deployments, even security hotfixes, cannot be deployed without needing to escalate and get into arguments Taking a generally antagonistic and hostile approach to communicating with the developers rather than again supporting them

nrmitchi 4y ago
> Taking a generally antagonistic and hostile approach to communicating with the developers rather than again supporting them This point is very ironic given your entire comment. It sounds like many of your complaints may be due to you not understanding the requirements that another team may have. You're complaining about costs and requirements that you are trying imposing on another team ($$, lax security). As an example, logging can get extremely expensive. A "better system" can't always fix an ungodly amount of unnecessary data. It might be best if you try to understand why they are working the way that they are. Trust me, they are not doing unnecessary work just trying to fuck with you.
- lloydatkinson 4y ago
  I’ve never complained about costs, read again. Strange you didn’t comment on any of the other points but decided the entire argument was incorrect because of two points.

nrmitchi 4y ago

> Taking a generally antagonistic and hostile approach to communicating with the developers rather than again supporting them This point is very ironic given your entire comment. It sounds like many of your complaints may be due to you not understanding the requirements that another team may have. You're complaining about costs and requirements that you are trying imposing on another team ($$, lax security). As an example, logging can get extremely expensive. A "better system" can't always fix an ungodly amount of unnecessary data. It might be best if you try to understand why they are working the way that they are. Trust me, they are not doing unnecessary work just trying to fuck with you.

lloydatkinson 4y ago
I’ve never complained about costs, read again. Strange you didn’t comment on any of the other points but decided the entire argument was incorrect because of two points.