this post was submitted on 07 Dec 2023
1417 points (92.1% liked)

linuxmemes

21207 readers
40 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
    [–] Kusimulkku@lemm.ee 24 points 11 months ago (1 children)
    [–] acockworkorange@mander.xyz 11 points 11 months ago (2 children)

    So two wrongs make a right? Or could this have been a civil private email instead? And if civil private conversations aren't working, then it's time to part ways.

    [–] pohart@programming.dev 4 points 11 months ago (1 children)

    A civil public email would have been fine.

    [–] acockworkorange@mander.xyz 3 points 11 months ago (1 children)

    Acceptable, yes. But a good manager knows not to shine a spotlight on the mistakes of the team. There's nothing to gain keeping it public that you wouldn't also gain by keeping it private. But your team's morale is kept high if you sing their praises instead of their shortcomings.

    [–] pohart@programming.dev 4 points 11 months ago

    I get what your saying, but i feel like the aggressively public development model means that more could be public here than i would accept on another team.

    [–] Kusimulkku@lemm.ee -1 points 11 months ago (1 children)

    This probably helped others not to make the same mistake

    [–] acockworkorange@mander.xyz 7 points 11 months ago (1 children)

    Of working with Linus? Yes, it probably did.

    [–] Kusimulkku@lemm.ee 1 points 11 months ago

    What? I'm talking about breaking userspace?