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.

It’s not even a good excuse because even if they did change their minds, he could still attempt to debate whoever it is on the scheduled date.

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.

I agree, this usage of it was bad.

Probably this.

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”.

Just switch to GNU/Hurd

/s

🤯

This is what I was thinking. For a first iteration to get out the door immediately it could just be windows with a “game browser” that launches full screen when you turn it on 😂

They change it all the time for funsies

Who’s Joe

The guy in charge of this place

No they’re not. And the tech literate people that will see that they can disable this protection and continue as normal.

Microsoft doesn’t always do good things, but I think this is fine. If you open firefox it’ll ask you if you want to set your default browser, and it won’t regedit for you. It will open up the proper windows menu that lets you set firefox as the default.

Not letting malware change your settings by default is a GOOD thing. It is also a good thing that advanced users can disable the feature.

The only bad thing about the story is the lack of transparency. Having to find out about it by breaking tools is bad. It would be better if they had a changelog for these updates that say what they do so admins can see if their tools will be affected.

You’re right, I’m not representing the merge correctly. I was thinking of having multiple merges because for a long running patch branch you might merge main into the patch branch several times before merging the patch branch into main.

I’m so used to rebasing I forgot there’s tools that correctly show all the branching and merges and things.

Idk, I just like rebase’s behavior over merge.

I like flutter’s design where you do your markup and styling as code, and then it gets rendered via opengl. So you get that native performance without having to deal with the whole browser stack.

I don’t like how almost all software these days is just web apps masquerading as native apps, but they’re just so damn easy to write compared to anything else.