Who Owns Deployments - Dev or IT? 152
txpenguin asks: "I am IT manager for a small software company. We host several generations of our applications in a fairly complex environment. Our systems are very much inter-dependent (clustering, replication, heavily loaded, and so forth), and bad changes tend to have a domino effect. Additionally, it seems that there are always those who need to be 'in the loop', but aren't aware of changes which affect them. There is a constant battle between IT and Development regarding who should handle the deployment of new code releases and database schema changes to production systems. Dev doesn't understand the systems, and IT does not know the code well. How do you handle this at your company? What protocols seem to work best? Can there be a middle ground?"
Re:Middle ground (Score:5, Funny)
Developers write code & documentation.
Installation/Deployment guides *are* required documentation.
IT takes the software, and follows the guide.
And in Magic Happy Land, that actually works without a problem.
Re:Middle ground (Score:1, Funny)
And then IT takes the lotion, and puts it on IT's skin.
Re:Middle ground (Score:3, Funny)
Re:Middle ground (Score:3, Funny)
Re:Speaking as a developer (Score:3, Funny)
I keep hearing people talk about "non-production hardware" - and it sounds like gibberish.
I asked my manager about this, and he snapped the pencil he was holding and started muttering something about "damn commies.". . .
Yes - there is a "Fantasy World" - it's where people are promoted into management for competence, and allocate sufficient resources for projects, and blue fairies ride on rainbows throwing bags of candy.
In the real world, we "test" - hell, we DEVELOP on production systems, that are mission-critical 24x7, with people's lives on the line. We get the axe when it doesn't work, and manager gets the bonus and the promotion when it does.
Welcome to the desert of the Real.