Too many alarms or alarms at unsocial hours? The engineering team should feel that pain.
Too hard to push? The engineering team should feel that pain.
Strange hard to diagnose alarms? Yep, the engineering team should feel that pain!
The feedback is very important to keeping the opex costs under control.
However, I think the author and I have different opinions on what DevOps is. DevOps isn't a full time role. It's what the engineer does to get their software into production.
I see a difference between a more definite operations team (SRE) vs an engineering team having responsibility for how their service works in production (DevOps).
DevOps is something that all teams should be doing - there's no point in writing code that spends it's life generating problems for customers or other teams, and having the problems arrive at the owners results in them being properly prioritized.
In smaller orgs, DevOps and SRE might be together, but it should still be a rotation instead of a fulltime role, and everyone should be doing it.
Engineers who don't do devops write code that looks like:
if (should_never_happen) {
log.error("owner=wombat@example.com it happened again");
}
Great if billing by the hour, and mostly unsustainable for products =3