I agree for the following reasons.

Imagine that you are a developer who has worked their heart out to build something as best they can with the information they are allowed to see.  How would you feel if your work was described as a turd lobbed over the wall?

Imagine that you are an operations guy carefully juggling resources to ensure that you have 24/7/365 uptime.  How are you going to feel if some resource hungry nightmare lands in production and you are told that it is now your problem for the rest of your tenure?

One deliverable, two miserable people.  The first toe in the water with DevOps I saw came about as a result of a heated discussion between the two parties.  The ops guys were pointing at their monitors proclaiming that the problems were obvious to anyone who could read a graph.  The DEV response was "Great, but you won't let us have access to those graphs and won't pay for the tooling in environments other than production.  It soon became apparent that the devs would be only too happy to lessen the impact of their development but what they had to predict impact was as much use as a horoscope.