AWS.
It’s taken off like a rocket in the .net world where I live even though c# support doesn’t seem marvellous and with Azure .net is the 1st class citizen and seems far easier to use.

But the really odd thing is I’m talking to the devs about how they use it and what they use, and it’s like a damn cult. They’re absolutely fanatical about it.
I don’t get it, it’s just a load of APIs, I just can’t get excited about APIs.

At my company the rest of the stuff, well that’s gone to shit and seems 10 years out of date. But it doesn’t matter because we use AWS and it’s the be-all-and-end-all.
FFS.

Normal behaviour.

(No pun intended)

Group dynamics form... In the worst case you'll end up with the cult where there is no (sane) decision making, rather ending up with whatever the majority wants.

@IntrusionCM seems like that’s what I might’ve joined.
If life will be easier drinking the kool-aid I might just drink a few pints of it and say “I was wrong everyone. This ten year old shit isn’t a problem after all, because it runs on AWS ! Silly me”

Getting a bit fed up of the IT industry, everyone seems to be an expert on everything.
I’m viewing Uber drivers with envy even tho the pay cut would be massive.

@TrevorTheRat

The thing in IT - and that's where I agree - is that people develop an insane cope mechanism.

They say: Yes we are aware of our technical debt.

Which translates to: But we don't touch it, god forbid, no one wants to tackle that pile of burning shit.

Instead they try to find all kind of non working solutions or hacks or workarounds...

They try to deal with the symptoms but leave the root problem untouched.

Which then ends up with all kind of crazyness... Going to the cloud while knowing that the solution which will be available via Internet has more security flaws than lines of code...

Putting everything behind Cloudflare / WAF and stating that is now secure (which is wrong for many reasons as Cloudflare can be compromised too and HTTP traffic even more)....

Scaling horizontally and burning tons of money though it is evident that the resources can never be enough.

Adding features and opening up to a large client base while the solution itself is a non scalable blob...

Burning money by buying licenses while the feature set of the products will be unused (Varnish, NGINX plus, ...)

Thinking big overall before thinking about priorities.

It's mostly just a giant catastrophic way to not deal with the simple conclusion that a burning pile of shit needs to be fixed.

@IntrusionCM I wish I could ++ this more than once because that’s exactly it

Azure is garbage, even if you use .Net
Shitty vms that takes ages to provision (autoscaling in the cloud is pointless if i can run to the store buy a server drag it to a data center, plug it in and install the software on it in less time than it takes azure to start a vm). It also doesn't help that their loadbalancers are garbage, but hey, atleast their prices are lower...

AWS isn't anywhere near as shitty. (Although it does cost a bit more)