Please advise on handling the existing geek

Question

Quick Story: I started a new job where everyone funneled their questions to 'the geek'. Being an experienced developer, I can do most of my assignments without consultation with the geek - thinks such as how to select the top 10 rows in a table.

Question: Is there a preferred way of handling these cases without offending the existing geek while ensuring the best solution gets implemented? My issue is the the existing geek is very young and makes a lot of mistakes, but still sounds authoritative because the other coders are just out of school and don't know better.

Answer 1

Just do your job. If your solutions are better then others will recognise this. If the existing geek objects then be prepared to back up your solutions with facts.

Answer 2

Invite him to the code review.

You don't want to offend him by going around him, but you should offer to get him involved in an appropriate manner. The code review is one such manner. I'm assuming his authority is informal and he's not actually the lead architect tasked with approving all designs.

Answer 3

Let them grow up. Everybody was young once.

In some years, they might be "a real geek".

Answer 4

Challenge the geek to a Klingon Duel. use the remains to decorate your office.

Answer 5

I agree with Jeremy, invite him to the code review.

Answer 6

You shouldn't be too afraid of offending the geek.

The way I understand your question, you feel a need to point out when he gives bad advice. I can see how you're uncomfortable with this, but in the long run, you'll be more uncomfortable if you don't speak up. Just make sure you have your facts ready, so nobody can accuse you of jealousy.

If you want to be a diplomat and avoid unnecessary gripe, try to identify areas where he is actually strong (most know something well), and make sure you ask him for advice now and then. In time, this should give you some room for criticism.

Answer 7

If you have ideas about how to improve things, email him and explain them. Be sure to copy the boss. This way he's in the loop and can participate, and you're also making it clear that you know what you're talking about.

Answer 8

Dude write a stored procedure that takes 4 hours to run. I wrote a sql statement that did the same things in a fraction of the time. His complaint: I am redoing work that has been tested and thus isn't a team player, is a loner, etc.

An answer then is to do what you're asked to do, and to change what you're asked to change.

I don't know the specifics of your business (priorities etc.), hower don't refactor things unecessarily.

If I'm team leader and I ask you to do something, I know there's a million things you could do, however I want/need you to do what I asked you to: so that that gets done, and there's less work left to do -- i.e. so that you're helping with the necessary/scheduled work. Similarly (depending on how much work it is to test/retest something) I might want you to avoid doing/changing anything extra: because your doing that would create more work (retesting), not less work.

Answer 9

I would definitely try and get a weekly development meeting going. Invite all coders/designers/line managers etc. This way you can ALL vent your frustrations out. Keep a record of what needs doing. This way the team can move forward together as a unit. I found this to be very useful last time I was in employment.

Good luck

Answer 10

Being on the other side of the fence and existing geek in my company. I sit with trepidation whenever we are interviewing someone new and highly talented, afraid that I will get shown up by the awsome intellect. That hasn't happened yet. I try to contribute to open source projects and there are people with so much knowledge that I often feel humbled. I consider myself not a team player if I fail to involve someone in the room in solving a problem or expressing an opinion, it is not their fault for being a loner. How was your interview experience with this company - was the geek in attendance ?