Hacker News Reader

Comment by inigyou | Hacker News Reader

Everyone went to "the cloud" because they want to make their IT problems someone else's problem. It's no different from the previous era of MSPs, except that there are now only, like, five MSPs in the world.

Note: I mean the Google Docs and Microsoft 365 type of cloud not the AWS and Azure type of cloud

View on HN

A symptom of the larger problem to want to divest and outsource everything not considered a "core competence". Hence the outsourcing of everything from housekeeping to IT

My take is it's actually because of poor performance of internal teams.

With a cloud provider, you can get an account by filling out a sign-up page and handing over a credit card. Internal teams will often hide behind Bureaucracy and a ticket system, with processes that make hosting a simple web app take multiple quarters.

Now there are layered reasons for that, some of them with legitimate basis, but at the end of the day they're usually low skilled teams click-ops-ing some VMWware, delivering a terrible service.

We were contemplating just this as a lunch time conversation among few engineers. Why can’t we have a sort of internal currency in the company and let teams use it as their “budget” to get things done? Infra team’s budget is broken up by the “user teams’ budgets + markup. Think your team needs a rlasticsearch cluster of your own versus the “managed” one by the infra team’s? Spend your budget accordingly. Want an increased budget? Get your director to pay from his currency budget.. all the way to the top..

That is already how many big corps work, still it doesn't avoid the move to cloud or offshoring.

Honestly, I think you're boiling the ocean there.

Internal hosting teams ( cloud or on-prem ) should work more like public hosting environments and should focus on:

- Segregating workloads. If amazon can host a hacked service on their hosting stack without every tenant immediately being compromised, you can too.

- Self-Service. Teams should be able to just get accounts and do stuff without asking anyone.

- Building assurance. Now you've made it easy for teams to do small things, you're more likely to get more users and have less shadow-IT. You can now try and build organizational assurance without making teams suffer.

A team just needs petty cash and a cost code for a small amount of space in dev land.

What everyone does instead if ask for the planning to be done and completed upfront, which isn't realistic for a team you just stood up trying to do UR and a POC.

Yea layer some more bureaucracy on there… i’m sure adding another sticking point will make it better

Reality of AWS or Azure in Europe : - Can't provision new ressources without calling them - If you get defects, you might be with Azure Europe Head after weeks of escalation and the only thing he wants to hear is if Microsoft can do a success story with you - Gaslighting you on issues

I agree with you, we went from terrible service, to terrible service with no leverage.

You also get internal cloud teams that "own cloud" taking away your ability to get accounts without going through the same all broken processes.

I’ve had this problem with azure in the US or the EU, but I’ve never really had this problem with AWS in Europe.

And now if you try to get a bug fixed or a new feature in GMail, it simply can't be done at all. Problem solved!

Because you could get a bug fixed in Outlook before?

Reply on news.ycombinator.com