> As for those conversations I had at devopsdays with the folks who thought they were “just” not devops enough?
As a junior, my vision of devops is someone who is guarding staging and production, and release management, assuming you have a mature self-service platform for developers. As for why people feel they are not devops enough I think it is important to realize that devops is mainly a culture change (quoting from a coworker). Your devops can be your system admin. Your developers should know how to handle some operations, because they will have to work with the SRE/devops. There should be a structure, a list of runbooks and procedures in place. Automation is only a syntactic sugar of blueprints, documentations, plans (recovery, backup, SLA, etc). DevOps should be the people that say NO to developer and NO to business and NO to upper management when you know something won't go well (e.g. there is a strict release/deployment requirements). So a mature DevOps team is essentially jack-of-all-trade go-to team. You write a lot, you talk a lot, you plan a lot, you maintain a lot, and you innovate a lot (looking at the big picture). Whether you are running a startup or an enterprise, automation is the last thing on your to-do list. To claify my last point: sure you should build your VPC and security groups using cloudformation if you are on AWS. But before doing that, you obviously need to start off with a discussion.
As a junior, my vision of devops is someone who is guarding staging and production, and release management, assuming you have a mature self-service platform for developers. As for why people feel they are not devops enough I think it is important to realize that devops is mainly a culture change (quoting from a coworker). Your devops can be your system admin. Your developers should know how to handle some operations, because they will have to work with the SRE/devops. There should be a structure, a list of runbooks and procedures in place. Automation is only a syntactic sugar of blueprints, documentations, plans (recovery, backup, SLA, etc). DevOps should be the people that say NO to developer and NO to business and NO to upper management when you know something won't go well (e.g. there is a strict release/deployment requirements). So a mature DevOps team is essentially jack-of-all-trade go-to team. You write a lot, you talk a lot, you plan a lot, you maintain a lot, and you innovate a lot (looking at the big picture). Whether you are running a startup or an enterprise, automation is the last thing on your to-do list. To claify my last point: sure you should build your VPC and security groups using cloudformation if you are on AWS. But before doing that, you obviously need to start off with a discussion.