3 ms·

It wasn't switching to the cloud that saved your dev team. It was getting rid of policy/thinking that allowed the "ownership" of a critical service to be so op

• re-thc 2y ago
  > It was getting rid of policy/thinking that allowed the "ownership" of a critical service to be so opaque/siloed that it took half a day to reboot a computer. No 1 got rid of any policy. Cloud meant any team could just take out their company card and sign up. Same as how SaaS got popular. The problem is, what is critical? That server was non-production and there were 100s to 1000s of things more critical to deal with. It was low priority. Maybe you know but to many up the chain in many orgs - they don't know. I've seen way worse scenarios - things on someone's laptop with ports opened that were production critical. Cloud isn't the cure, you're right, but it forced a lot of change.
  • Kon-Peki 2y ago
    > Cloud meant any team could just take out their company card and sign up > Cloud isn't the cure, you're right, but it forced a lot of change. That's the thing - there are plenty of organizations that operate solely in the cloud but do not give their teams the authority/ability to spend without prior approval. And there are plenty of organizations that have no cloud presence that allow their teams the discretion to spend money when spending money is the right answer. For a lot of companies, the move to the cloud was a super large benefit. I'm just arguing that the real benefit to those organizations was a side effect and that many organizations probably still don't realize this.