| The way I've seen things work is like this: devops sets up something convoluted that they for some reason like. Developers are confused by the thing. It causes them endless problems. Documentation is sparse, or out of date, or just plain wrong. The instructions to fix problems omit key requirements because the person who wrote them just assumed the reader knows about X and Y when the reader often has no clue. You follow the instructions and the problem is not solved, and maybe to make matters worse, you run into new problems. The way I see it is: if developers enjoyed dealing with infrastructure, devops jobs would not exist, it would just be something that developers do as part of their job. As a devops engineer, you should think of your fellow software engineers as your users, not as your "project members". Your job is to make it as painless and problem-free for them as possible. If problems arise constantly, that's not the user's fault; that's your fault. |