this post was submitted on 19 Jul 2024
35 points (100.0% liked)

linuxmemes

21162 readers
1355 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!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 1 points 3 months ago (3 children)

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

    [–] [email protected] 2 points 3 months ago (2 children)

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

    [–] [email protected] 0 points 3 months ago* (last edited 3 months ago) (2 children)

    And who pushes out production updates on a Friday!

    [–] [email protected] 1 points 3 months ago
    [–] [email protected] 1 points 3 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.

    [–] [email protected] 0 points 3 months ago

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

    [–] [email protected] 0 points 3 months ago (1 children)

    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.

    [–] [email protected] -1 points 3 months ago

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

    [–] [email protected] 0 points 3 months ago (1 children)

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

    [–] [email protected] -1 points 3 months ago

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