reflectedodds

Confirmed

The shareholders probably care, but to the layman, expecting 6.61 billion and only earning 6.49 billion doesn't amount to much. They're not going anywhere.

tldr, not sure if it was bullet or shrapnel from the bullet.

I don't know why you're being downvoted here. I thought a lot of the audience here was relatively informed on what it's like to work in IT/programming. Where we do what we can to make sure all our updates go well, but things slip through the cracks.

This was a massive fuckup, but it's likely not that different than pushing a bug to prod, it just so happens that their prod has such a huge audience. I would hope they have very strict rules about what gets in, but I can also respect that no matter how many processes you put in place to make sure bad things don't happen, problems can still make it through.

Crowdstrike should be held to a higher standard of course, because of how impactful these mistakes can be for their software. And it's pretty crazy that something this bad slipped through. But I wouldn't jump to criminal negligence here without more information.

p.s. I'm not saying CEOs / corps should not be held accountable. They should be. And CEOs do have the power to drive the company into criminal acts and they should be held accountable with jail time for that. I'm just saying I don't think that's the case here.

Probably this.

I agree, I also pay pros for work I can't/won't do. But I don't tell people that I did it. It's just something that bugs me.

A big peeve of mine is when someone says they did something, "I remodeled my floors, I painted the walls, I fixed my car, i put in a fence", when they really mean they hired people to do these things. It's straight up taking credit for other people's work and it's normalized.

I grew up poor where hiring help was rare so when someone said they did something, they always said it proudly and they meant they did it themselves.

Now I always ask and point out they didn't do anything. I'm really fun that way. But honestly i think the language matters. For big jobs i personally say I had the walls painted or I got the car fixed since that implies getting someone else to do it.

Microservice from the start may be a lot of overhead, but it should at least be made with that scalability in mind. In practice to me, that just means simple things like make sure you can configure it via environment vars, run it out of docker compose or something because you need to be able install it on all your dev systems and your prod server. That basic setup will let you scale if/when you need to, and doesn't add anything extra when planned from the start.

Allocating infrastructure on a cloud service with auto scaling is the hard part imo. But making the app support the environment from the start isn't as hard.

Skilled in asking a chatbot how to job.

as soon as you pay for 12 consecutive months, you will receive this perpetual fallback license providing you with access to the exact product version for when your 12 consecutive months subscription started.

So at most your software will be 1 year old.

AWS has so much documentation, and yet it never has what I'm looking for ☠️

In our testing, the VPN always continued to report as connected, and the kill switch was never engaged to drop our VPN connection.

This is the only place they mention kill switch. I feel like it needs a slight clarification on whether it was enabled and didn't work, or if was just disabled and therefore not "engaged".