3 ms·
> development team's operational posture (e.g. run books, alarming, monitoring. Isn't DevOps in large part forcing the developers to have responsibility over t
by calvinmorrison 4y ago
> development team's operational posture (e.g. run books, alarming, monitoring.
Isn't DevOps in large part forcing the developers to have responsibility over the code they push and giving short and frequent pushes to easily rectify problems?
Making developers do support work reduces support in the long run because they'll get frustrated and automate solutions.
- stetrain 4y agoYeah, I feel like the term has been taken over to mean using kubernetes and having continuous deployment pipelines for your microservices. My understanding of root of the term is about ownership and responsibility, where the team that develops the app also owns how the app deploys and runs in production, including monitoring and responding to issues. If the team decides that the right way to deploy their app is once every two weeks using a shell script and a zip file, cool. As long as it's documented and monitored so you know if it's working.
- calvinmorrison 4y agoYeah, what's worked well for me is having ops or security people draw up guidelines (for security, it may be something as trivial as require ssh key auth, for ops it may be: write a script that matches an existing deployment procedure and we can get your app up and running very quickly).
- lazide 4y agoAnd/or become burnt out and develop a severe ‘learned helpness’ complex. It depends on the environment they’re in, and if they have the tools and support to be able to fix issues. Many companies, they don’t.