![]() Silos exist because you had to have specialized knowledge to operate your specialized infrastructure. The network exists to connect everything to the rest of the world, and as technology wore on the network became the transport for the infrastructure to talk to everything else. The computer got bigger and bigger and eventually morphed into a virtualized hypervisor. The direct-attached storage became NAS and eventually SAN. ![]() The more we deconstructed the mainframe, the more we needed to focus. Instead of one giant machine we had lots of little special machines everywhere. When we busted the mainframe apart and started down the road of client/server computing the hardware started becoming more specialized. Everything was connected to the mainframe. There weren’t any silos with mainframes because everyone pretty much had to know what they were doing with every part of the system. Think about the original compute resources – mainframes. The silo mentality came about when we started getting more specialized with regards to infrastructure. But what if I told you that DevOps was just another silo? Team Playersīefore the pitchforks and torches come out, let’s examine why IT has been so tribal for so long. It focuses on the only pure thing left in the world – committing code. The DevOps mentality doesn’t reinforce teams or silos. ![]() The savior has finally arrived! DevOps is the silo-busting mentality that will allow us all to get with the program and get everything done right this time. It’s a viscous cycle of mistrust and playground cliques.Įxcept for DevOps. The network team is a bunch of jerks that don’t like anyone. The server teams don’t care about the storage team. The storage team doesn’t care about the network. We keep hearing how IT is too tribal and broken up into teams that only care about their swim lanes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |