I'm opposed to distinct dev ops teams. Deployment and management has to be an integral part of the programming team. Regardless of what it's called, it's as you say, if it's distinct it'll just be throwing code over the fence.
The team writing user features should be the same one coming up with the deployment. It's terrible to have somebody coding database features without having a clue about the install and management of that database. It's equally terrible to have somebody managing a DB that doesn't understand, or is unable to contribute to the code that works with that DB.
As more things move to distributed computing (shared services, virtual hosts, serverless, etc.) it becomes ever more important to stop segmenting these programming roles. Sure, you can have specialties, but the ownership of code must be shared across the board.
There should be no fence.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm opposed to distinct dev ops teams. Deployment and management has to be an integral part of the programming team. Regardless of what it's called, it's as you say, if it's distinct it'll just be throwing code over the fence.
The team writing user features should be the same one coming up with the deployment. It's terrible to have somebody coding database features without having a clue about the install and management of that database. It's equally terrible to have somebody managing a DB that doesn't understand, or is unable to contribute to the code that works with that DB.
As more things move to distributed computing (shared services, virtual hosts, serverless, etc.) it becomes ever more important to stop segmenting these programming roles. Sure, you can have specialties, but the ownership of code must be shared across the board.
There should be no fence.