this post was submitted on 07 Dec 2023
1478 points (91.8% liked)

linuxmemes

21025 readers
731 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
     

    An oldie, but a goodie

    you are viewing a single comment's thread
    view the rest of the comments
    [–] thisisnotgoingwell@programming.dev 5 points 10 months ago

    Honestly, whether or not we agree with the approach of Linus, these kind of disagreements happen in the real world. Tensions run high. Recently I've been on calls where things need to be implemented this month, during a time where most of our resources(engineers) will be on vacation. These kind of conversations can be important to have to make sure this doesn't happen again. The project management team got their ass handed to them for kneeling to the LOBs' ridiculous timeline expectations. And they were told to hold the L if things don't work on the go-live date, there will be no post implementation support until mid January if something doesn't work.