5 ms·
I agree with you, being in the same position. I wonder if the DevOps trend started because of the constant friction between devs and ops. While devs main concer
by clagio 8y ago
I agree with you, being in the same position. I wonder if the DevOps trend started because of the constant friction between devs and ops. While devs main concern and job is to deliver new features, ops main concern and job is to keep things stable. These different goals caused ops to be seen as an obstacle to dev job. Being the devs close to the business was easy to predict that we would be taken out or at least required to change. I think, we (ops) are mainly the one to blame for the current situation and now we can only adapt or die.
- de_watcher 8y agoIt has become manageable to do both for one person.
- kacbskjbc 8y agoUnfortunately, it's only really possible when you stand on the shoulders of massive companies like Amazon and Google, at which point you're not really doing "dev" and "ops", you're just doing "dev" and outsourcing "ops" to a big company that'll only do half the work for you.
- romeisendcoming 8y agoUsing recipes, pre-built images, automation, and mostly opaque system controllers that abstract away all the underlying detail. That isn't a reliable/secure system and only salesmen and those who have a stake in that model push it. Unfortunately this is the new normal, fait accompli.
- Bombthecat 8y agoBut not allowed in many many organizations and firms. Governance and security forbid people to be op and dev in one person. Or God forbid: control the dev, pre stage and production environment.