IME, yes.

I'm currently working as an SRE supporting a large environment across AWS, Azure, and GCP. In terms of issues or incidents we deal with that are directly caused by cloud provider problems, I'd estimate that 80-90% come from Azure. And we're _really_ not doing anything that complicated in terms of cloud infrastructure; just VMs, load balancers, some blob storage, some k8s clusters.

Stuff on Azure just breaks constantly, and when it does break it's very obvious that Azure:

1. Does not know when they're having problems (it can take weeks/months for Azure to admit they had an outage that impacted us)

2. Does not know why they had problems (RCAs we're given are basically just "something broke")

3. Does not care that they had problems

Everyone I work with who interacts with Azure at all absolutely loathes it.

Things like this are usually a systemic failure rather than being 100% attribute to a single person.

Honest question: Do they actually _want_ to live-and-breathe software, or do they work in a highly competitive and highly compensated environment where doing that is implicitly required?

Is that actually true (the bulk of people in the tech industry are working in "big tech" or startups)?

I don't know if there's any hard data around this, but my understanding has been that people working for these types of companies are maybe a single digit percentage of all tech workers (if that).

People working for those companies are certainly the most vocal online, though, which maybe skews perception.

I guess Amazon pulled out of the project halfway through, since for the last ~2 years there's been a half-finished building just sitting there completely abandoned in our town center.

We've had 100% success in reducing Dependabot noise by disabling it in our repos. Why should we pay this guy to configure it for us and still end up with Pull Requests being opened?

I don't see if mentioned in TFA, but if new human teeth can be grown is it expected that the new ones will just grow in "correctly" to fit a person's mouth?

The practical problem with this is that many large organizations have a security/infosec team that mandates a "zero CVE" posture for all software.

Where I work, if our infosec team's scanner detect a critical vulnerability in any software we use, we have 7 days to update it. If we miss that window we're "out of compliance" which triggers a whole process that no one wants to deal with.

The path of least resistance is to update everything as soon as updates are available. Consequences be damned.

Literally the first sentence.

This must be a regional thing?

I live in New England and I always see kids out and about with no adults around supervising. Especially from 1-3PM on weekdays when school lets out. Maybe a side-effect of walkable infrastructure.

I tried the major ones (Adderall, Ritalin, Vyvanse, Concerta, etc.). They all made dealing with ADHD significantly easier, but even at the lowest doses they turned me into an extremely anxious and irritable person. I had never experienced anything close to a panic attack or nervous breakdown in my 30+ years of being alive until I started taking stimulant medication.

I decided that living with untreated ADHD was the better alternative, so now I'm back to copious amounts of coffee to deal.

This has never been the case in any company I've ever worked at. Even if you can finish your day's work in, say, 4 hours, you can't just dip out for the other 4 hours of the day.

Managers and teammates expect you to be available at the drop of a hat for meetings, incidents, random questions, "emergencies", etc.

Most jobs I've worked at eventually devolve into something like "Well, I've finished what I wanted to finish today. I could either stare at my monitor for the rest of the day waiting for something to happen, or I could go find some other work to do. Guess I'll go find some other work to do since that's slightly less miserable".

You also have to delicately "hide" the fact that you can finish your work significantly faster than expected. Otherwise the expectations of you change and you just get assigned more work to do.

The way to deal with this is with an org-level Service Control Policy that enforces the tagging standards.

A resource doesn't have the right tags associated with it? It can't be created.

https://docs.aws.amazon.com/organizations/latest/userguide/o...

Comments URL: https://news.ycombinator.com/item?id=44203014

Points: 18

# Comments: 1