Didn't we invent the word "devops" specifically for the combination of work of development and ops? How did we get to the point where we now need a word for "development without the ops"?
That's still not what this is about. Take the example in the article: people who don't write code 100% of the time but have to think about mechanical and electrical engineering consideration for most of the time. You don't describe that as DevOps.