Comment by hyperman1

I've seen the world begore devops, and it wasn't that pretty either. We had 2 silos. Devs had a bunch of apps, ops too. Devs had no idea what the hardware did, ops had no idea what the software did. Users suffered, and assigning responsibility was impossible.

The dev in me hated throwing an app over the wall, only to hear about ops completely misconfiguring it. Or ops ignoring deployment guidelines and mucking up releases. Or getting a db with 2 records and being expected to test performance. Or getting complaints about prod crashing, but no logs, eror messages, or any kind of access, and ops couldn't notice that disk full might be a disk being full.

The ops in me hated devs being loose with passwords, asking huge mountains of resources, and getting apps thrown over the wall at me without any idea what to expect. Or devs logging sensitive stuff.

For me, devops was good for breaking up the silos. We wanted to have a group of people cooperating on a group of applications. Some people will have a dev or ops profile, and that's fine. People should respect that others know more of some aspects. But: no one should shield the applications from everybody else in such team. Everybody should strive to learn enough basics to understand both perspectives and priorities.

Starting a devops silo is just the worst possible option.