4 ms·
> you should have devs, admins, qa, business analysts working together The idea of DevOps is to my knowledge that the role of Developer and Operator slowly mer
by awesomeMilou 3y ago
> you should have devs, admins, qa, business analysts working together
The idea of DevOps is to my knowledge that the role of Developer and Operator slowly merge together in one role. Which would also be in line with SCRUM and agile development, i.e everyone should at some point be able to do everything in the stack, if it's necessary.
What you're describing sounds more like the standard agile development process.
- adamhp 3y agoAnd the growth was really driven by the great exodus to service oriented and microservices architectures from monolithic webservers deployed to Tomcat and the like. The author in the OP really nails it when he talks about the ever-growing complexity of modern tech stacks. It necessitates this blurring of the lines.
- zokier 3y ago> The idea of DevOps is to my knowledge that the role of Developer and Operator slowly merge together in one role That is certainly not how devops was originally envisioned.
- dijit 3y agoPeople downvoting this guy are misinformed. There are two major sources for DevOps: 1) the 10+ deploys a day talk from Flickr: https://www.youtube.com/watch?v=LdOe18KhtT4 https://www.youtube.com/watch?v=LdOe18KhtT4 which is where most of the actual methodology comes from. 2) The "DevOps Days" (first use of the portmanteau by Patrick Dubois) which was an agile conference aimed at Systems Administrators trying to get them to work more agile; the conference was called "DevOps" to make developers think it was also for them. Neither of these primary sources said that we should erode or replace ops people; or that it was ever intended to be a role or individual responsibility. This is a lie that corpo's have made to reduce headcount.