Source: devops.com
DevOps Was Supposed to Kill Developer Jobs. Here’s Why it Didn’tCategory: automation, artificial-intelligence
Home » Blogs » DevOps Practice » DevOps Was Supposed to Kill Developer Jobs.
By Bernard Brode on July 17, 2020Leave a CommentThe rise of DevOps is more an evolution than a revolution, and developer jobs aren’t going anywhere
The first is that, although none of these approaches (and arguably even DevOps, as we’ll see below) have developed into distinct disciplines, they have subtly redefined the way in which developers are understood by the average organization. The second is that, in this context, many developers have begun to stress that they have cross-cutting expertise.
On the other hand, DevOps has had huge effects on the way that developers work, because it points to the skills that the best developers have.
By Bernard Brode on July 17, 2020Leave a CommentThe rise of DevOps is more an evolution than a revolution, and developer jobs aren’t going anywhere
The first is that, although none of these approaches (and arguably even DevOps, as we’ll see below) have developed into distinct disciplines, they have subtly redefined the way in which developers are understood by the average organization. The second is that, in this context, many developers have begun to stress that they have cross-cutting expertise.
On the other hand, DevOps has had huge effects on the way that developers work, because it points to the skills that the best developers have.
Related Articles
Community Partners
DevOps Careers