2 ms·
It’s an own goal, why not have infrastructure as a sibling team to the dev team. This is a problem only because I make it a problem, situation
by zaphirplane 2y ago
It’s an own goal, why not have infrastructure as a sibling team to the dev team. This is a problem only because I make it a problem, situation
- alephnerd 2y agoThis is an organizational structure that is common industry-wide. Core IT (not Infra - Infra often means DevOps/Platform which is part of R&D), like any other shared function, is placed under the CFO/COO org because it is a shared internal function that's used to keep the lights on. These are functions that by definition are a cost center, and as such R&D really doesn't want to own it, as it distracts from the core mission of delivering forward facing features. The whole point of the DevOps/Platform Eng model was to incorporate operations under R&D, but having R&D own and manage physical assets is a major distraction, and a major reason Public Cloud became popular among plenty of companies. Cost of compute isn't the only variable that comes to play - depreciation, hiring/firing, security, redundancy planning (because these are physical assets), etc are all significant headaches operationally and financially. Technology is a tool - you choose the tool that works best. In some cases Public Cloud is the solution, in other cases it's a CoLo. It comes down to your specific organization's needs.