It's sad that people still think DevOps was about teaching people "dev and ops skills". There isn't even such a thing as "ops skills". Ops stands for Operations - as in Operations Management, a job that has nothing to do with servers (it's a job focused on ensuring business continuity in any industry). The term "Operations" got associated with servers and server commands because the department that Systems Administrators worked in was called the "IT Operations" department, aka, ensuring the business continuity of the Information Technology department. All of this happened because the entire industry spontaneously became collectively ashamed of the term "Systems Administrator" and "sysadmin". But they still wanted a way to refer to "the server people" and "what server people do", so they started saying "ops".
The "Ops" in DevOps was intended to mean the department itself, not the tasks they performed. The idea that devs should be learning or doing Systems Administration is the same as a building architect learning/doing concrete pours. They should know about concrete and the pouring/curing process, but they don't (and shouldn't) be pouring and smoothing the concrete themselves.
The "Ops" in DevOps was intended to mean the department itself, not the tasks they performed. The idea that devs should be learning or doing Systems Administration is the same as a building architect learning/doing concrete pours. They should know about concrete and the pouring/curing process, but they don't (and shouldn't) be pouring and smoothing the concrete themselves.