Live data from Hacker News

Keeping Your Company Asshole-Free

blog.hackfwd.com

1–10 of 55 posts

Re: Keeping Your Company Asshole-Free

#4

I find it amazing how many people in a team don't share their insights, assets or experiences with the team. Why is that? Is it fear?

A saw a post on Twitter a couple of weeks ago from a guy who was in his last week of his job.

He claimed his employer was trying to "milk him" by asking for a handover guide for the next person taking over the role.

I think that people hold onto information for power, to protect their position and to give them leverage over their situation.

Re: Keeping Your Company Asshole-Free

#7
post #4

I find it amazing how many people in a team don't share their insights, assets or experiences with the team. Why is that? Is it fear?

A saw a post on Twitter a couple of weeks ago from a guy who was in his last week of his job. He claimed his employer was trying to "milk him" by asking for a handover guide for the next person taking over the role. I think that people hold onto information for power, to protect their position and to give them leverage over their situation.

I think you're right. Like Klaas said in the presentation, such behavior usually is a reaction to the working ethics of the company. Screwing your colleagues (and the company) is rewarded by (lousy) management or management with a hidden agenda.

Re: Keeping Your Company Asshole-Free

#8

I find it amazing how many people in a team don't share their insights, assets or experiences with the team. Why is that? Is it fear?

Most frequently it is because they are in a competitive environment and fear that they won't be given credit for their contribution.

Re: Keeping Your Company Asshole-Free

#10

I find it amazing how many people in a team don't share their insights, assets or experiences with the team. Why is that? Is it fear?

In my experience, which, granted is limited (3.5 years programming), one or two team members I work with very rarely share their insights.

In the case of these team members I think one comes down to fear of maybe looking daft in front of the rest of the team by saying something that they think might be wrong. The other can just be a sanctimonious prick and will ask people questions that they simply wont know the answer to, to show them up in front of the rest of the office.

So in my experience fear is certainly a factor holding a person back. However on the flip side a person lording his knowledge over other people but not sharing it in a useful way conducive to improving the general programming knowledge of the team.

They both harm the team but in different ways. I don't know how these two problems can be solved though. Maybe encouraging opinion from the people who fear sharing their points of view and being supportive of them would help.

I'm at a loss though with regards to the power-bitches that like to make people look small with their own knowledge.

Post reply on HN