β² 1411 βΌ Linus does not fuck around (lemmy.one) submitted 2 years ago by AdventuringAardvark@lemmy.one to c/linuxmemes@lemmy.world 490 comments fedilink hide all child comments An oldie, but a goodie
[β] Kusimulkku@lemm.ee 28 points 2 years ago (1 child) So is breaking the userspace permalink fedilink source parent hideshow 2 child comments replies: [β] acockworkorange@mander.xyz 12 points 2 years 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. permalink fedilink source parent hideshow 4 child comments replies: [β] pohart@programming.dev 6 points 2 years ago (1 child) A civil public email would have been fine. permalink fedilink source parent hideshow 2 child comments replies: [β] acockworkorange@mander.xyz 3 points 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [β] pohart@programming.dev 5 points 2 years 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. permalink fedilink source parent [β] Kusimulkku@lemm.ee 2 points 2 years ago (1 child) This probably helped others not to make the same mistake permalink fedilink source parent hideshow 2 child comments replies: [β] acockworkorange@mander.xyz 9 points 2 years ago (1 child) Of working with Linus? Yes, it probably did. permalink fedilink source parent hideshow 2 child comments replies: [β] Kusimulkku@lemm.ee 2 points 2 years ago What? I'm talking about breaking userspace? permalink fedilink source parent
[β] acockworkorange@mander.xyz 12 points 2 years 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. permalink fedilink source parent hideshow 4 child comments replies: [β] pohart@programming.dev 6 points 2 years ago (1 child) A civil public email would have been fine. permalink fedilink source parent hideshow 2 child comments replies: [β] acockworkorange@mander.xyz 3 points 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [β] pohart@programming.dev 5 points 2 years 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. permalink fedilink source parent [β] Kusimulkku@lemm.ee 2 points 2 years ago (1 child) This probably helped others not to make the same mistake permalink fedilink source parent hideshow 2 child comments replies: [β] acockworkorange@mander.xyz 9 points 2 years ago (1 child) Of working with Linus? Yes, it probably did. permalink fedilink source parent hideshow 2 child comments replies: [β] Kusimulkku@lemm.ee 2 points 2 years ago What? I'm talking about breaking userspace? permalink fedilink source parent
[β] pohart@programming.dev 6 points 2 years ago (1 child) A civil public email would have been fine. permalink fedilink source parent hideshow 2 child comments replies: [β] acockworkorange@mander.xyz 3 points 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [β] pohart@programming.dev 5 points 2 years 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. permalink fedilink source parent
[β] acockworkorange@mander.xyz 3 points 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [β] pohart@programming.dev 5 points 2 years 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. permalink fedilink source parent
[β] pohart@programming.dev 5 points 2 years 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. permalink fedilink source parent
[β] Kusimulkku@lemm.ee 2 points 2 years ago (1 child) This probably helped others not to make the same mistake permalink fedilink source parent hideshow 2 child comments replies: [β] acockworkorange@mander.xyz 9 points 2 years ago (1 child) Of working with Linus? Yes, it probably did. permalink fedilink source parent hideshow 2 child comments replies: [β] Kusimulkku@lemm.ee 2 points 2 years ago What? I'm talking about breaking userspace? permalink fedilink source parent
[β] acockworkorange@mander.xyz 9 points 2 years ago (1 child) Of working with Linus? Yes, it probably did. permalink fedilink source parent hideshow 2 child comments replies: [β] Kusimulkku@lemm.ee 2 points 2 years ago What? I'm talking about breaking userspace? permalink fedilink source parent
[β] Kusimulkku@lemm.ee 2 points 2 years ago What? I'm talking about breaking userspace? permalink fedilink source parent
