Bad Apples
I am a Sr business Operations Analyst, and I manage a team of 5 developers. One of them is bad apple. His intellect is high , he is a brilliant programmer, but he cant seem to focus and is distracted by the silliest things. If only I can get him to focus for 30 minutes...............
I am a bad apple as well. I do not like to see people fail. Instead of delegating and holding people accountable ( aka my bad apple) I sacrifice my time to make sure they succeed. I am terrible at this , I have worked for the last 28 days without a day off ( 15 hours a day) just to make sure my guys do not get behind.
I am a bad apple as well. I do not like to see people fail. Instead of delegating and holding people accountable ( aka my bad apple) I sacrifice my time to make sure they succeed. I am terrible at this , I have worked for the last 28 days without a day off ( 15 hours a day) just to make sure my guys do not get behind.
Quote:Original post by Trapper Zoid
I've never had any problem with team members being "too brilliant" if they use their abilities for the good of the team. The danger is if they start thinking that only they have the ability to do the work and they turn into "The Maverick", a close relative of the Prima Donna. A maverick will take a large chunk of the project that "only they" can solve and go bunker down for a while to work on it. The problem I've had with these types is they always take too much and make very bad estimates on how long they will take. Eventually the rest of the team is twiddling their thumbs waitng for the maverick to finish their bit, or getting shot down when they try to help.
Shit, that's me. Problem is, I'm often right about being the only one who can do the work (or at least, anyone else would take several times as long and be constantly bugging me with questions). It's depressing, you know, forcing yourself to realize how long everything REALLY takes :)
Quote:Original post by Dmytry
edit: btw. I did experimental mavericking on my prev job for a week or two (on management request), to figure out how much time it'd take to single handedly recover a startup (we had 2 programmers left at that moment, me and other guy who's still mavericking as far as i know), and did quit. Having management that thinks you're superhuman (merely because most other employees sucked badly, were fired/did quit, and you're the last hope) is tad annoying.
I would say that a startup that has two programmers and also has identifiable "management" personnel at all, is too top-heavy to have a chance at success. :/
Quote:Original post by ZahlmanQuote:Original post by Dmytry
edit: btw. I did experimental mavericking on my prev job for a week or two (on management request), to figure out how much time it'd take to single handedly recover a startup (we had 2 programmers left at that moment, me and other guy who's still mavericking as far as i know), and did quit. Having management that thinks you're superhuman (merely because most other employees sucked badly, were fired/did quit, and you're the last hope) is tad annoying.
I would say that a startup that has two programmers and also has identifiable "management" personnel at all, is too top-heavy to have a chance at success. :/
yea, that's what I thought too. It had more programmers to begin with though, that was the near end situation. Two programmers whom weren't paid for a month and have to decide to continue working in hope that start-up recovers, or not.
[Edited by - Dmytry on February 21, 2009 8:30:22 AM]
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
