Did I miss the memo on DevOps?

Question

I thought DevOps was an effort to allow a team to own the entire "product" or application from design, development, and delivery.How many folks are in organizations where DevOps is a separate team deploying and running their products/applications/microservices?What are your thoughts and feelings about keeping these functions siloed vs allowing full ownership of the outcomes?(I mean sure it's easy and nice to throw stuff over the fence and not have to worry about directly dealing with poor coding and design/error handling issues...)

not_your_vase · Accepted Answer

I hate maintaining devops tools. Never in my life managed to update Jenkins without breaking half of the plugins (many of which are no longer available for the updated version, and the rest became incompatible with the original config. Oh, and Jenkins refuses to start anyway, because it hates that the JVM patch version doesn't end with a 4-digit prime).
I also hate when I just want to run an overnight test on a VM, which should be a 10 minutes long task to set up (and to shift-delete in the morning), but with a separate devops team it takes 2-3 days, with a lot of back and forth ticket-comments and approvals.
I just can't win with devops.