1131
you are viewing a single comment's thread
view the rest of the comments
[-] Diplomjodler3@lemmy.world 41 points 5 months ago

I really don't want to be the guy responsible for this fuck up

[-] Robin@lemmy.world 37 points 5 months ago

For a company this big it would also have to have gotten past a code review and QA team, right? ... right? ...

[-] Diplomjodler3@lemmy.world 18 points 5 months ago

Of course, of course. This is how these things are always done.

[-] possiblylinux127@lemmy.zip 11 points 5 months ago

I like how they kept on pushing the update for hours

[-] Bremmy@lemmy.ml 10 points 5 months ago* (last edited 5 months ago)

And who pushes out production updates on a Friday!

[-] yrmp@lemmy.world 6 points 5 months ago

We do.

"If something goes down over the weekend, fewer people see it" - my leadership team.

I guess Asia can report the problem on Sunday and I'll get a nastygram and fix it that afternoon.

[-] possiblylinux127@lemmy.zip 5 points 5 months ago
[-] merc@sh.itjust.works 4 points 5 months ago

Code review, QA team, hours of being baked on an internal test network, incremental exponential roll out to the world, starting slow so that any problems can be immediately rolled back. If they didn't have those basics, they have no business being a tech company, let alone a security company who puts out windows drivers.

[-] qjkxbmwvz@startrek.website 19 points 5 months ago

Yeah, something this big is absolutely not one engineer's fault. Even if that engineer maliciously pushed an update, it's not their fault


it was a complete failure of the organization, and one person having the ability to wreck havoc like this is the failure.

And I actually have some amount of hope that, in this case, it is being recognized as such.

[-] Diplomjodler3@lemmy.world 3 points 5 months ago

I agree but they will still blame it all on that one guy.

[-] merc@sh.itjust.works 9 points 5 months ago

No they won't, not if they're in the slightest bit competent.

Blameless post-mortem culture is very common at big IT organizations. For a fuck-up this size, there are going to be dozens of problems identified, from bad QA processes, to bad code review processes, to bad documentation, to bad corner cases in tools.

There will probably be some guy (or gal) who pushed the button, but unless what that person did was utterly reckless (like pushing an update while high or drunk, or pushing a change then turning off her phone and going dark, or whatever) the person who pushed the button will probably be a legend to their peers. Even if they made a big mistake, if they followed standard procedures while doing it, almost everyone will recognize they're not at fault, they just got to be the unlucky person who pushed the button this time.

[-] jlh@lemmy.jlh.name 12 points 5 months ago

This is an industry wide issue. This is just the first symptom.

[-] possiblylinux127@lemmy.zip 6 points 5 months ago

What we need is to stop the blind trust

[-] Diplomjodler3@lemmy.world 5 points 5 months ago

Yeah and that means they won't nail some poor schmuck to the wall over this?

[-] explodicle@sh.itjust.works 6 points 5 months ago

He'll just get fired, apply somewhere else, and they'll only know the dates he worked at CrowdStrike.

If anybody cared, they would have switched away from M$ by now.

this post was submitted on 19 Jul 2024
1131 points (96.9% liked)

linuxmemes

21282 readers
373 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 2 years ago
    MODERATORS