An oldie, but a goodie
this post was submitted on 07 Dec 2023
1480 points (91.9% liked)
linuxmemes
21453 readers
900 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
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
sudoin 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!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
As many seem to have overlooked itb this is from more than a decade ago.
And to those setting "not being toxic" == "being vague":
Suggestion if you're in a situation: separate the subject discussed from the person and, to the contrary to what is said in some other posts, be very specific!
Improvised example:
Hey all,
patch xyzz and its aftermath communication is unacceptable.
It's content is not to the standards we have set here (explain).
Even worse, in the communication aftermath we blamed behavior of user space applications for bugs that are within our domain instead of owning up.
The bugs within the kernel will be focused on with highest priority by a, b and myself.
For the communication: (consequences). As explained the patterns shown here are unacceptable.
I have decided to no longer have x as a kernel maintainer on our team/enforce pairing for all communication/set up stricter consequence catalogue. Any specific action,really...
Not perfect as it's very early here, I haven't slept well and I'm not deep into the topic.
Just remember to separate subject to be discussed from person(s) acting please.
And always remember: bad communication is really easy and a lot of managers trained that their whole life! ♥
Reading this version I wouldn't know the writer is deeply disappointed, frustrated and angry. It's good you're trying to improve the letter but this is exactly what many people don't like about it: it changes the meaning. Perhaps you could include a paragraph which conveys this, such that the reader understands the gravity of the situation better.
Oh that was in purpose! It shouldn't matter that I personally am angry. My employees should never NEVER try to prevent me from being angry but focus on doing the best job they can.
That's what I admire about Linus: he realized the negative impact his anger had on the performance of others - and fixed it!
To be clear: I can be angry - but my anger isn't the reason I want things to change. Being angry is MY FAILURE as manager!
Think about it in another way: do you want your colleagues do things they thin prevent you from being disappointed, frustrated or angry - xor do you want then to move your collective goal forward no matter what you'd think.
Another example: if I'd be the one to have caused this communication mess I'd want my employees to call me out - even though I will get angry the moment I realize I've fucked up big time!
Ignoring emotions is very unhealthy. I understand that it is seen as desirable in a business context, but it is very unhealthy and detrimental in the long run.
I wouldn't necessarily call it ignoring, if you just... don't explode on someone in a "professional" letter, if we can call it that.
I agree! Making someone aware of your feelings doesn't mean exploding. You can just tell them. "I am very sad, frustrated and angry due to your actions. Please don't do this again." Is very clear and hurts no one.
I apologize - it wasn't my intention to imply that at all! Emotional self management is a critical skill for managers - and that shouldn't mean "go away, emotions!". A trainer and coach I highly respect phrased it simply: "emotions are. They exist if we like them or not.".
What I intended to convey was "do not use a public platform to channel your emotions."
If this would've been a private conversation I would integrate an explanation of my current situation, feelings and context for my reaction. And also this sounds abstract it can totally be a "dude I'm absolutely pissed. I need you to work with me through this." (this works btw in both meanings of "pissed" ;)).
I think removing someone's maintainer status does communicate disappointment in their performance quite well.
And as for anger and frustration, these things really don't matter in this circumstance. Work is not therapy. If you need to vent anger and frustration, get a therapist. Employees are employed to do their job, not to be the emotional punching bag for a manager who can't control their temper.
If an employee doesn't perform to expectations repeatedly and even after you had a few constructive one-on-ones, then demote them or fire them. No need to vent your anger on them and lose your professionalism.
Tbh, the first time a boss of mine loses their temper and verbally attacks a colleague like Linus did here, they have also lost all of my respect for them. And at that moment I will start to look for another job.
I am not and was not advocating for venting - just for communicating emotion. This can be as simple as:
"Your actions have deeply frustrated me and caused great anger on top of [technical reasons]. I would ask that you be more careful in the future."
This ensures the reader not only understands they hurt Linux with their actions but also another human being. Many people will be more careful if they know they caused personal pain to an actual human being and not just to an abstract technical object such as a codebase.
I know I am going against established cultural norms in western business context - please don't disregard my proposal just because it contradicts established culture.
I do understand what you mean, and it makes much more sense than advocating for venting.
But I still feel that putting emotions into a discussion about work performance isn't the right way, especially when done in public.
In a situation like that where something caused a lot of negative emotions (that go beyond your work performance is bad), I think you should have two separate talks. One about the factual things where one is boss and the other is employee, and one about the hurt/emotions the behaviour caused and in this talk, both are just people resolving their personal problems.
Something like the issue in the OP really shouldn't cause anger on Linus' side, since it's a totally factual issue. A propper response would have been to decline/revert the change while publically saying "This change validates that rule of the project" and then privately contacting the maintainer in question and tell him, "We talked about this repeatedly, if you don't stop, we need to take consequences."
Emotions should really only enter the picture when personal offenses where comitted before or maybe if the employee did something with the intent to hurt the project/company/manager.
But if you get really angry because your employee did something wrong, then that's a problem on the side of the manager and not on the side of the employee.
That said, I think it's totally ok to tell the employee about the consequences of their actions ("We lost X amount of money" or "It took Y amount of time to correct it" or something like that).
I agree with what you said in general.
This is probably taught in manager courses in order to protect their subordinates from managerial outbursts, which is a good cause, but they're not quite right.
The Linux kernel is Torvalds life work. He literally spent most of the time he has on this planet on it, as did thousands others. Instead of watching his children grow, he made sure the planet gets a great operating system. It takes immeasurable effort to keep a vast software project in a good state - most large organisations with many times the resources fail to do so.
The maintainers behaviour represents a complete disregard for this sacrifice. They are showing through their actions that they don't care that Torvalds and many others spent the little time they have on this planet on this software project instead of more fulfilling and joyful activities. I cannot imagine many more hurtful or disrespectful insults than this. It's not far from saying their efforts are null and thus their life wasted.
I am saying all of this because I feel that you are speaking as a leader in a company, where you make sure other people's money is spent productively. This not at all the same thing as what Torvalds is doing, because it's not just a job, it is his literal life or life's work.
This doesn't excuse the behaviour, obviously - but it makes it very human. It's good that he changed. I just hope we can find a middle ground between forced business speak and emotional outbreaks.
I'm not a manager (used to be team lead, but managing is not for me), but I've worked under a few coleric managers and some that where able to communicate in a sensible way.
One of my bosses, for example (that was the job where I was team lead) had a pretty similar style of communication as Linus.
Sure, the company was his life work. But I also started there shortly after the company was founded and I too spent a lot of time and was very emotionally invested in the company and the products. And my boss was just human (and on top didn't know a lot about the subject), so he made mistakes. And his judgement was often wrong.
But he was never able to accept that he made any mistakes. He'd offload all his mistakes onto some employee, while claiming that every idea that worked out was his, and not the idea of the employee who actually had the idea and had to convince him first. And every time something went wrong, he'd slam the door of some employee open and shouted and swore at that employee.
Turns out, that's not a great way to encourage people working there. Most of the good people quit after one especially bad explosion of his.
Back to Linus: is it human to be angry that someone disagrees with you? Maybe.
Is it in any way helpful to anyone? Clearly not.
I am pretty sure that anyone who gets to be a maintainer on the Linux kernel is heavily invested and has sacrificed a lot to get there. Attacking them like Linus did, that really renders their life work worthless.
The maintainer did nothing with the purpose to harm the Linux kernel project. He just accepted a change that he thought would improve Linux. Disagreeing on a factual topic with your boss should never trigger an explosion like that.
I would disagree just because the success of the product (be it closed or open source) shouldn't be dependent on the feelings of one person. You can be frustrated and angry, but it's more useful to explain why you feel that way and what can be done to address it. Including your feelings only makes the person not want to do what specifically hurts you, not what is best for the project.
Why not both?