3 ms·
As a person that works in DevOps (but doesn't write YAML files all day), the problem is using the wrong solution for the scope. I think DevOps groups a lot of
by 100011_100001 4y ago
As a person that works in DevOps (but doesn't write YAML files all day), the problem is using the wrong solution for the scope.
I think DevOps groups a lot of times end up doing the work that the groups they support should have done for themselves. However, the working yourself out of a job is a very real thing. This is happening with DB Admins and QA primarily. Cloud technologies is displacing the rest.
If your company has 1 dev, 1 sys admin, 1 DB admin and 1 QA person, creating a DevOps team won't produce more efficiency, it will have the opposite effect.
On the 10x complexity comment, if DevOps is done correctly it's invisible to the user. In practice any decision made automatically has drawbacks. On the flip side, a lot of developers are unaware how things work or lack consistency that automation can put in place.