If you build something that DevOps can use, then there is no problem. I can't tell you how to navigate the waters from the start of the project to success -- t

If you build something that DevOps can use, then there is no problem. I can't tell you how to navigate the waters from the start of the project to success -- that's all dependent upon the people involved and requires a fair amount of people skills to do well. On the other hand I've seen enough "convenient for developers, impossible for devops solutions" to know that sometimes developers lack the background to get it right. Couple that with a bit of hubris and you get the classic, "Well, I did my job. It's not my fault that devops are clueless and can't do their job". I'm not in any way saying that this is what you do. How could I know one way or the other? I'm just saying that it's a pretty common occurrence in my fairly extensive experience (hint: all my hair has been grey for a decade and I still work as a programmer ;-) ). Thus my answer: No, having problems with DevOps is not being a "diva". Ignoring the problems of DevOps so that you can have things easier for you is an unfortunately common, but none-the-less disastrous approach. Are there teams where DevOps are inflexible at the cost of everybody else involved? Of course, that's common too: hence the "No".