Steve Jobs left because he lost a corporate power struggle. Sam Altman was fired because the board thought he was too fundamentally untrustworthy to remain as CEO (if we're to believe their statement ofc).
Hugs going out to the teams at Instructure working to fix this. I've been through a similar Ransomware attack (national news stories, lots of customers dead in the water, etc.), and it's about as bad a situation you can wind up in.
It's going to depend on the type of team and environment you work in. Probably on how senior you are as well.
If your boss asks you for specific documents and expects a quick turnaround, and you regularly take 3 weeks or whatever to produce them, then yeah probably.
If your boss generally leaves you alone to find and solve problems on your own, then probably not.
>Is Azure really this unreliable? There are concrete numbers in this blog. For those who use Azure, does it match your external experience?
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.
Firing someone for an honest mistake is a great way to make all of your employees afraid to push changes out of concern that they'll be next (although to be fair this was a pretty big mistake).
Things like this are usually a systemic failure rather than being 100% attribute to a single person.
>before I went to elite companies, where it is quite normal for people to live-and-breath software, at almost all hours.
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?
>It is true IF you live and work in the Bay Area, Seattle, and TLV - which represent the bulk of tech industry employment.
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.
Same here. A local grocery store and several other local businesses got bought out and demolished so Amazon could build a new Fresh store.
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.
This is why you shouldn't waste your money on expensive "consultants" like this guy.
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?
Aren't the shape/size/placement/etc. of human teeth fairly unique across different individuals? At least unique enough to use dental records to identify bodies.
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 thing to do is to monitor your dependencies and their published vulnerabilities, and for critical vulnerabilities to assess whether your product is affect by it. Only then do you need to update that specific dependency right away.
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.
>Welcome to America where you must watch the kid every second until they turn 18
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.
Steve Jobs left because he lost a corporate power struggle. Sam Altman was fired because the board thought he was too fundamentally untrustworthy to remain as CEO (if we're to believe their statement ofc).
Different kinds of "controversy" IMO