> When it comes to application development and deployment, we think it is important to distinguish between the parts that developers are responsible for, and th

> When it comes to application development and deployment, we think it is important to distinguish between the parts that developers are responsible for, and the parts that operations is responsible for. Otherwise, if these roles get muddled, it would result in communications mishaps, bugs, or even service outages. Isn't this is the complete opposite of general wisdom these days? If development and operations are split then you end up with two departments working against each other. Development are assessed on their ability to deliver features and operations are assessed on their ability to keep the service running. So development are incentivised to push for as rapid deployment as possible, and operations are incentivised to resist deployment as much as possible (because deployment can lead to downtime).