Smart jerks aren't worth it
The article highlights the negative effects of toxic personalities, particularly "smart jerks," on software development teams, advocating for respectful collaboration and the importance of interpersonal skills in hiring practices.
Read original articleThe article discusses the detrimental impact of toxic personalities, particularly the "smart jerk," on software development teams. It challenges the myth of the "difficult genius," suggesting that while some believe that such individuals are necessary for innovation, cohesive and respectful teams can achieve great results without toxic behavior. The author defines a "jerk" as someone who is intentionally aggressive and dismissive, leading to negative emotional experiences for their colleagues. Excuses for tolerating such behavior, such as the individual's unique knowledge or productivity, are critiqued as misguided. The article emphasizes that toxic behavior stifles creativity, drains energy, and demotivates team members, ultimately harming overall productivity. It suggests that while some smart jerks can change, organizations must establish boundaries and prioritize team dynamics. The author advocates for hiring practices that focus on both intelligence and interpersonal skills, and highlights the importance of training in soft skills for developers. The conclusion stresses that the costs of tolerating toxic behavior outweigh any perceived benefits, urging teams to either help the individual improve or decide they are not a good fit. The article serves as a reminder that successful development teams are built on respect and collaboration, rather than the presence of difficult personalities.
Related
The 10x developer makes their whole team better
The article challenges the idea of the "10x developer" and promotes community learning and collaboration in teams. It emphasizes creating a culture of continuous learning and sharing knowledge for project success.
No Matter What They Tell You, It's a People Problem (2008)
The article emphasizes the crucial role of people in software development, citing teamwork, communication, and problem-solving skills as key factors for project success. It highlights the importance of job satisfaction and team cohesion, underlining the significance of positive personal relationships within development teams.
A dev's thoughts on developer productivity (2022)
The article delves into developer productivity, emphasizing understanding code creation, "developer hertz" for iteration frequency, flow state impact, team dynamics, and scaling challenges. It advocates for nuanced productivity approaches valuing creativity.
Software engineers are not (and should not be) technicians
The article delves into the distinction between software engineers and technicians, advocating for automation in software development. It warns against prioritizing predictability over automation to foster innovation and efficiency.
There's the pitch.
Most of the time people aren't trying to be jerks. They're just not having a need met. They may or may not know about the need, or may or may not be working to address it. It may be something that you're responsible for that you're not acknowledging.
Don't underestimate how far a little humility, open ears, and boundary setting might get you. Writing the person off as a jerk just makes the problem worse.
Not to say you're responsible for anyone elses bad behavior, but it's also not ok to pin all the problems of team dynamics on one person. Having a emotionally healthy productive team is a lot of work, and it's a group effort.
I've always kept that lesson in mind since and it's never led me astray. Companies that put up with those personalities just aren't worth it.
Every time I've seen it shared, it was shared by a plain-old, regular jerk.
Why, Star Trek is basically that. Or at least used to be.
It’s great that they get along, but they don’t accomplish much, if anything.
For every such article you could write one called "Short String Isn't Worth It."
Obviously, depending on your context, working with difficult people is necessary and worth it. Sometimes it may not be worth it to you, but it's worth it to other people.
Lots of people at Apple did not want Steve Jobs to return, after he left. But lots of people did, and he arguably made everyone there (whom he didn't fire) a whole lot of money. Was it worth it or not? Depends how you feel about things.
Articles like this can be better written when the author reminds himself to focus on the elements and forces, rather than reifying and polarizing the topic into a garish stereotype.
The point of an article like this ought to be to help people examine themselves and their situation so as to reconcile themselves to it or to take productive action. Pitchforks and torches aren't helpful.
If I'm going to spend 40+ hours a week interacting with someone, I'm not going to hire a brilliant jerk. I don't care if they're great at their job. If I'm going go spend most of our time together wanting to scream at them, I don't want any part of it. No thanks. Life's too short to spend it around jerks.
Genius is a blessing, yes, but it is often a burden. "Genius" implies bright talents but may imply deficits, too. Either way, this person didn't necessarily ask for that, and may struggle to express their ideas in a way which isn't combative. Genius in one area (say, programming) does not always follow in another (emotional regulation).
We should be humane with people as they grow. Indeed, the single best aspect of the mind is that it can change when it wants to.
For every smart jerk there's a manager who endorses that person and who also has a manager who in turn either has the same attitude or "lets them cook" as long as KPIs are fulfilled.
People will generally downplay toxic behaviour if they exhibit it themselves. Not saying that's always the case, but in my experience it's much more common than management being intimidated enough by the jerk to not want to touch them.
I'd take a genius jerk vs. any regular dude, the conversation may be unpleasant but at least interesting.
>Let's define the term "jerk" here as someone who is both intentionally, and obnoxiously aggressive. Aggressive in their enforcement of their own opinions and dismissive of others'. Obnoxious in the frequency of unnecessary negative interactions with them. Intentional in that they understand their behavior is aggressive, and choose not to adjust it.
Intent is impossible to prove (or so I've been told). He uses the implicit heuristic of, "They keep doing it." However, it (obnoxiously aggressive behavior) is in the eye of the beholder (or, often, in the appearance of the accused). What is "frequent" and "unnecessary"? By who's metric? What's the line between "opinionated" and "browbeater"? Does it shift depending on the identity of the individual? (Yes.)
>Ultimately, you know you're dealing with someone who is acting like a jerk by how you feel after interacting with them.
This criteria is just asking to be abused by people who hold prejudice. Some people are irrational or traumatized, and it's okay to sympathize with their take on an individual while also understanding that they're not being reasonable. Likewise, it's possible for a charismatic and energetic individual's behavior to be deleterious; coworkers don't necessarily walk away feeling overtly attacked, but their tendency to self-police to the bully's desire might be raised. Such jerks often also zero-in on "fair targets", leaving them as the only people to feel abused, while everyone else rationalises their treatment as deserved.
IME, the best way to root out actual jerks is to focus on people with power (by however mechanism, they are able to get people to do what they want them to do, more so than those people are able to get them to do things) who are quick (within one or two negative interactions) to blackball others (maintains a sh*t list, ghosts, verbally harasses, particularly in a way that isolates the target).
Instead focus on behaviours, I've seen frustrated people raising genuine problems labelled as a jerk.
For example, is the guy who picks up on issues in code reviews the one who is a jerk?
Others ... not so much.
One thing that they all had in common, though, was not suffering fools. Sometimes, they would yell and cuss, other times, they would just never work with you again.
I generally preferred the first.
I won't do it to others, because that's not my style, but I would get a dressing-down, followed by "Don't let it happen again." I'd still be in the Circle. I haven't been ejected from the game. If they just transfer me out, I'm down for the count.
I have found, that, if we want to be top of the game, then we need to work with those that are already there. We have to take the risk that we will be rejected, or told that we're not doing a good enough job. We should definitely not expect participation trophies. In fact, it's likely that we may not get a huge amount of positive feedback.
Pretty darwinian, but that which does not kill you, makes you stronger.
I feel that a lot of the lessons that I learned, also helped me to be a better leader and mentor. Some of those lessons, were on what not to do.
That’s abuse of authority AND dunning-kruger
If most interactions leave you feeling emotionally exhausted, dismissed, belittled, or angry, you may be dealing with toxic behavior on your team.
Or you’re that kind of person who’s hiding its stupidity behind being nice with others and doesn’t produce anything of value. You are often responsible for the feelings you have. A well-functioning, cohesive, happy team can come up with novel solutions, better implementations, and well-reviewed code.
That would deserve another myth-busting article… No team is happy and productive The fact that they are inconsiderate of others does not make them more logical.
One doesn’t always know what triggers others. It could be anything. A better solution is to strengthen yourself mentally, to be less impacted emotionally by others.Related
The 10x developer makes their whole team better
The article challenges the idea of the "10x developer" and promotes community learning and collaboration in teams. It emphasizes creating a culture of continuous learning and sharing knowledge for project success.
No Matter What They Tell You, It's a People Problem (2008)
The article emphasizes the crucial role of people in software development, citing teamwork, communication, and problem-solving skills as key factors for project success. It highlights the importance of job satisfaction and team cohesion, underlining the significance of positive personal relationships within development teams.
A dev's thoughts on developer productivity (2022)
The article delves into developer productivity, emphasizing understanding code creation, "developer hertz" for iteration frequency, flow state impact, team dynamics, and scaling challenges. It advocates for nuanced productivity approaches valuing creativity.
Software engineers are not (and should not be) technicians
The article delves into the distinction between software engineers and technicians, advocating for automation in software development. It warns against prioritizing predictability over automation to foster innovation and efficiency.