Live data from Hacker News

Avoiding “Smart Guy” Syndrome on Team Projects

programmers.stackexchange.com

21–28 of 28 posts

Re: Avoiding “Smart Guy” Syndrome on Team Projects

#21
post #18

Earlier quoted context omitted.

So the thing is that your eyelids are probably the only thing on your body that you cant look at, even with a mirror. I know that's supposed to be the point of your comment, but I cant relate how.

Not if it's tattooed in reverse and you close your eyes in the light. Just sayin ;)

But if I understand correctly, human eye can't focus on things that close to them.

Re: Avoiding “Smart Guy” Syndrome on Team Projects

#23
post #21

Earlier quoted context omitted.

Not if it's tattooed in reverse and you close your eyes in the light. Just sayin ;)

But if I understand correctly, human eye can't focus on things that close to them.

That quote is the Chuck Norris of proverbs - even tattooed in reverse on my eyelids, I can still be inspired by it :-)

Re: Avoiding “Smart Guy” Syndrome on Team Projects

#24
I can very much relate to being the uncomfortable smart guy. And it's not about "being right". What bothers me is not when there’s a discussion that I come short out of, but when no one bothers to respond because then it seems like no one cares about the project as much as I do.

Related to this I think is that I don't really see problems as problematic, but interesting. I actually enjoy twisting and thinking about every possible solution, and lately I've started to realize that a lot of people (especially managers) don't have the same associations to the word problem. So previously pointing out problems and thinking every body would be exited about them, turned out to be a very counterproductive approach.

Re: Avoiding “Smart Guy” Syndrome on Team Projects

#25
You can be right - but your maturity is determined by your response when the team "comes around" to your idea. A mature developer nods, and immediately begins walking through their pre-developed action plan. That person has the confidence that the team knows there was a mistake, and no need to walk through the past.

An immature developer throws out the "I told you so" and lauds it over their team.

We all make mistakes, it's the foundation for the fail-forward-fast mantra. So acknowledge the mistake, impress others that you have a solution, and move forward.

Re: Avoiding “Smart Guy” Syndrome on Team Projects

#26
Make the best case you can for adopting course of action X to solve potential problem Y. Then step back and let the person in charge make the decision.

My rule of thumb is two 'No' answers. It goes like this:

Present affirmative reasons why direction X is the right choice. Try to focus on the benefits of X rather than pointing out the flaws in the current plan. If the response is no, I'll try to address any concerns regarding X. If the response is still no I leave it alone.

I've found that if you continue past this point it becomes an argument. Now you're challenging the groups ability to proceed after making a decision. Once that occurs your opinions are an impediment to the groups progress.

Note: Perspective is worth 80 IQ points. The team could be basing the decision on factors you aren't aware of. The world is seldom simple enough to present one 'best' answer to a given situation.

EDIT: No they aren't "all against you because you're so much smarter than them". Seeing this sentiment in some of the comments. Trust me this doesn't happen. For every one real instance of this, there are 100 instances of condescending engineer who is just parroting the technology fad of the day. Or is an architecture astronaut.

To anyone who feels this way regularly ask yourself "How many times have I felt like this? In school? In college? At job 1? At job 2?" Either the world is wall to wall jerks, or you're the jerk.

Re: Avoiding “Smart Guy” Syndrome on Team Projects

#27
post #21

Earlier quoted context omitted.

Not if it's tattooed in reverse and you close your eyes in the light. Just sayin ;)

But if I understand correctly, human eye can't focus on things that close to them.

if you are near-sighted you can.... I think.

Re: Avoiding “Smart Guy” Syndrome on Team Projects

#28
post #10

When I was a kid and went to a new school, I was the best in class at math. Mathematical ability is pretty clear cut, so there is no room for "yeah you thought you were awesome, but in reality you were just a know-it-all." I really was that good. :) In that class, there was a girl who used to be best at math before I came. She didn't like that I blew her out of the water when it came to calculating. Though she wasn't…

Maybe the B leader avoid to recruit A class programmer.
Post reply on HN