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.
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.
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.
So is breaking the userspace
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.
A civil public email would have been fine.
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.
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.
This probably helped others not to make the same mistake
Of working with Linus? Yes, it probably did.
What? I’m talking about breaking userspace?