writes: Even in the best of organizations, the development and operations departments have friction. Each has its own goals, metrics for success, and team culture. Plus, ops is in the business of making things predictable and unchanging, while developers are in the business of changing everything. Those opposing priorities make it harder for dev and ops to communicate freely. Despite the industry’s ongoing efforts to bring the communities together, developers continue to grumble about ops, who simultaneously grumble about devs.
Grumbling doesn’t help to resolve the tension (or desire to throttle someone). Understanding does. So both developers and sysadmins were asked to imagine that they were granted a single wish: You have the power to give your company’s [ops team | development team] an understanding of one thing — just one thing — that currently irks you. What spell would you cast with that magic wand?
The results are in two articles: 3 Way Ops Can Help Devs: A Developer Perspective and 3 Ways Devs Can Help Ops: An Operations Perspective. Maybe it's not surprising that the shared component is: Listen to each other more. Share what you're up to, and what the goal is. (Kumbaya optional.)
But maybe some of the specifics can help you grok where the other folks are coming from. For instance:
As a developer named John writes, “Software development sometimes needs to be allowed to bend the rules/regulations in order to operate efficiently/quickly. Too many times, the rules (e.g., who has access, when, what can be installed, etc.) cause ridiculous delays in cycle time for development or support.”
A classic example is when developers assume always-on connectivity. “The network is not a static monolith that never changes,” one ops staffer noted. “We’re planning a data center network upgrade. It will require disconnecting every server and reconnecting them to the new switches.” That could cause some apps to think the entire world has ended and crash in an untidy heap.
Would you have included different magic spells?