Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Sounds similar to the theory that to be a successful CEO you need to be an asshole


But do you need to be an asshole to become a (successful) CEO, or does the job turn you into one?


In order to meaningfully answer this question, we need a much more well-articulated definition of "asshole". People's definitions vary widely. For example, suppose you see someone broadcast online about being very distressed about a problem and your response is to point them toward resources that might be useful to solve the problem -- some set of people would consider you an asshole for that pattern of behavior. Some would consider it very helpful. Is it? Not my point. The point is that there is disagreement.

In order to become a successful CEO (or team lead or spouse...), you do need to be able to muster the emotional backbone to have tough conversations with people. One thing that can hold you back from this is the internal worry about being an asshole. Unless you are able to say to yourself, "I hear a voice on my shoulder telling me I'm a terrible person. But this topic needs to be discussed and I need to do advocacy here. This is uncomfortable and I don't like it but I'm going to do it anyway", you will under-communicate and issue won't get resolved.

However:

1) It is possible to err. That difficult conversation? Might in fact just be you being an asshole. We are not lucky enough to live in a world with a 100% surefire way to avoid this. So, good communication involves being willing to risk some probability of being an asshole.

2) People without that "maybe you're being an asshole" voice are not going to have this problem.


Being an asshole has a lot more to do with the tone of the message than with the content.

In my experience, most people will accept feedback if you do it in a respectful manner.

You can tell someone they are underperforming without insulting them. Respect your employees.

Even when you tell people to read the manual, you can do so in a way that doesn’t feel insulting. There’s a world of a difference between “RTFM!” and “I believe the documentation addresses this problem on page X.”


> Being an asshole has a lot more to do with the tone of the message than with the content.

Bingo. God I wish more software developers realized this. Being open with criticism is important. But for most people who are not a very certain type of programmer, we don't want to hear the criticism given with words like:

"What were you thinking? Are you stupid? Of course you don't do x."

and

"I've found through experience that it's important to do X, because if you don't, then Y happens."

The fact that I run into so many people on software developer teams that communicate in the former manner has led me to leave traditional software development in favor of data analysis where I don't have to work on a team of 5-6 people, of whom 2-3 are complete assholes.

Plus, if you want to know why there are so few women in programming, this alone is a huge factor. Yes, there are a very few women who can give and take criticism in the abrasive fashion I outlined above, but most women prefer to give and take criticism in the polite, productive manner of my second example. Once again, the criticism is the same in both examples, all that's different is the tone.

Too many people in the software development industry have taken Linus Torvald's communication style as something to emulate.


Totally agree. And this amplifies the effect I mention above. If your picture of “steadfastly advocating for something important” is using an abrasive tone and not assuming good faith or intelligence, you’re going to be more likely to be either aggressive or passive not assertive


This is way more difficult in person than it is online in writing. And the fear of getting it wrong can increase with each time that you actually do get it wrong (leading to you replaying the event in your head, eg).


If you're actually worried or concerned about how you're communicating, you're probably fine or at least acceptable.

It's the people who are either oblivious to the need to carefully communicate who are the difficult ones, along with those who intentionally ignore societal norms in an effort to prove their "alpha" status.


> If you're actually worried or concerned about how you're communicating, you're probably fine or at least acceptable.

I think I've finally realized how to articulate what my frustration with statements of the form "If you're worried about X, you're fine" is. The person presenting the worry has a prior of [I am worried about this]. They then go seeking a solution that will let them alleviate the worry by taking concrete steps to address it. When they run into the advice "If you're worried, you're fine", they have two problems:

1) If being worried is the only reason why they are at least acceptable, then to continue to be acceptable, they need to continue to be worried.

2) They haven't actually gotten a concrete action to take or thought exercise to go through. That means if the commenter is wrong and they actually do have a habit to work on, the only thing they might be doing differently is telling their intuition (system 1 for the Khanemann fans) "Hey, you know that alarm? turn it off." Their intuition probably doesn't listen very well and probably keeps them worried, but it is also no longer acting as a useful signal whatsoever of the problem.

----

The approach I would take is to come up with a list of actually-answerable questions to ask myself, to have faith in my intuitions on those questions unless I get concrete evidence that they are wrong, and then to work to make peace with the remaining discomfort. For example, when driving a car:

- Buy a wide-angle rear-view mirror so you have better spatial awareness.

- When opening any car door from the insite, habitually practice doing the Dutch reach.

- When you are aware of a cyclist, know the reference points on the car that you should keep them at so you are a safe passing distance.

- Don't do anything else besides perhaps converse with another human in the car while I'm driving.

- Practice scanning my environment while driving and other generally-safe driving habits.

- Having practiced your duty of care -- Accept the reality that at some point I might end up crushing another person's ribcage and snuffing out the life of someone's father/brother/aunt/teacher -- a fellow human.


Not when you're so worried about how you'll be perceived that you soften your statements beyond comprehension. And yes, this absolutely happens, and no, you probably don't realize if you're doing it.

Try re-reading a peer performance review you've written after the fact. It can be eye-opening.


I believe the organization Toastmasters exists just for this purpose.

You can replay an event in a supportive feedback group instead of in your head.

(I've never been to a Toastmasters' meeting, but have heard their sales pitch.)


Speaking of Steve Jobs..




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: