Back in 2014, the DevOps model was strongly criticized for putting unnecessary additional pressure on developers. It was said that DevOps deprived developers of being able to specialize in what they do best: crafting code.The common picture associated with DevOps in those times was an exhausted techie running around because he had to dabble in QA / testing, systems administration, database management, and whatever else.
So it’s like those good old school days when you’re trying to dominate everyone else’s efforts, in pursuit of your A+.On the contrary, the DevOps approach reminds you of the college times when everyone is chipping in united by a shared goal. DevOps not only generates crucial concepts and tools to create automated workflows but also boosts the integration of team collaboration tools to these workflows.
The Bottom Line
Love it or hate it, the DevOps approach has caused irrevocable changes in the tech world. And instead of going against the stream, it’s better to embrace complementary DevOps practices, thus improving operational productivity, quality, and revenues as well.
