Slashdot Mirror


Motivating Your Co-Developers?

3flp asks: "We've heard all about those coding projects where 90% of the code is done by one person. Unfortunately, on my current project it's me :-(. It's a comms DSP project with a lot of C & some assembly. My team of 4 will hopefully produce about 20k lines of code. Now comes the problem: we just got to our first small integration stage (we do try to do them early & often), and it turns out the other guys have got nothing. No code. I want to ask Slashdotters, people who have the experience with small software projects, how would you go about it? How to bring other less experienced coders up to your level and beyond? Or at least how to make them suck less, and if they get stuck on something, to just come and bloody ask for help?" This is something almost every developer has had to deal with. For those of you who have experienced this, what did you do about it and how did things turn out?

"Deadlines are super-tight (what else is new)... but all 'my' parts are ready on time, and I enjoy what I'm doing. After about a month of design and two weeks of coding, I've got about 50% of my software features. The others definitely do understand the requirements and the design, because we had plenty of discussions. 'All right, lets get what you've got so far, we'll just try the interfaces, even if your code doesn't do anything much yet.' 'I haven't tried to compile it yet.' Then I looked at the little code they've produced, and it's a disaster (abhorent coding style, serious logical mistakes, etc). Obviously, these guys understand the 'domain' problem (I would think that's the hard part), but suck at coding (which is apparently the really hard part for them).

Hiring new people this late in the project won't work, as anyone who has read 'The Mythical Man Month' knows. On this project, I have a de-facto role of a software team leader. Before, I've always been just a coder, not responsible for others. So okay, I'm doing fine with my part of coding, but that's no use. If others don't catch up quickly, we'll have serious problems delivering on time. I need to stop hacking on 'my' part of code, and help elsewhere. They definitely do understand the requirements and the design, because we had plenty of discussions. 'All right, lets get what you've got so far, we'll just try the interfaces, even if your code doesn't do anything much yet.' 'I haven't tried to compile it yet.' Then I looked at the little code they've produced, and it's a disaster (abhorent coding style, serious logical mistakes, etc). Obviously, these guys understand the 'domain' problem (I would think that's the hard part), but suck at coding (which is apparently the really hard part for them).

Obviously, I need to look into some way of helping or motivating, but without putting them off. I could just take over someone else's module and code it in no time. But if anyone did that to me... well that's out of the question."

22 of 537 comments (clear)

  1. How to motivate your codevelopers: by johnthorensen · · Score: 5, Funny

    Block "http://www.slashdot.org" at the firewall :)

    -JT

    1. Re:How to motivate your codevelopers: by Anonymous Coward · · Score: 2, Funny

      Even better, redirect them to goatse.cx when they type in slashdot.org. That will stop them!

    2. Re:How to motivate your codevelopers: by Polo · · Score: 4, Funny

      Or maybe redirect all slashdot requests to just this article... ;)

    3. Re:How to motivate your codevelopers: by scotch · · Score: 3, Funny
      Plus sex with interns is usually better and easier!!!

      --
      XML causes global warming.
    4. Re:How to motivate your codevelopers: by HP+LoveJet · · Score: 2, Funny

      ...so they can start spending their time constructing a microwave relay connection on top of the building or in their office window.

      --
      spawn_of_yog_sothoth
  2. Re:Use XP by groundhog00 · · Score: 1, Funny

    send them all to XP Agile programming conference in chicago.. then when they come back.. fire their asses.

  3. fire them by Anonymous Coward · · Score: 1, Funny

    Fire their sorry asses, then ask for a raise. Then fire the incompetent bozo who hired them.

  4. Re:The perfect motivator by Kowgod · · Score: 2, Funny

    No no no no no. The perfect motivator is donuts, and the possibility of MORE donuts, to come.

    --
    -- Mesmer is the Dairy King Remove your panties to email me.
  5. Re:The perfect motivator by Budgreen · · Score: 3, Funny

    know where I can get a hammock?

    --
    The greatest right given is the right to be wrong...
  6. Hire me instead by LordNimon · · Score: 3, Funny

    Emebedded system, C and assembly? The other developers can't write code fast enough? If youre company is in Austin, TX, may I suggest that you fire one of them and hire me instead? I can assure you, you won't regret it.

    --
    And the men who hold high places must be the ones who start
    To mold a new reality... closer to the heart
  7. Re:Don't motivate... by R2.0 · · Score: 5, Funny

    "One excuse I've heard is that if you don't have enough evidence that someone is not being productive and you fire them, they can sue you (WTF, I highly doubt that). "

    Allow me to introduce you to the term "At Will" employment. That means that one is employed at the will of the employer. If the employer loses the wiil to employ someone, they can be let go with no reason whatsoever.

    HOWEVER...

    Thia only applies if one is male, white, under 40, has no disabilities that fall under the scope of the ADA, and (in some states) straight. If you are not one of these, you fall into a "protected class" and, although one can still be fired, the employer needs to document it REALLY well.

    --
    "As God is my witness, I thought turkeys could fly." A. Carlson
  8. Kinda like that Dilbert Cartoon by qurob · · Score: 2, Funny



    Dilbert

    "Did you write that code for me yet?"

    "No. I'm one of those people who needs to be threatened every day, or else I won't do anything"

  9. Re:Don't motivate... by MadCow42 · · Score: 4, Funny

    Have a coding contest...

    1st place is a new Cadillac
    2nd place is a set of steak knives
    3rd place is "you're fired"...

    It's worked before...

    q:]

    MadCow.

    --
    I used to have a sig, but I set it free and it never came back.
  10. Re:The perfect motivator by Anonymous Coward · · Score: 2, Funny

    Well, there's The Hammock Hut, over on Third...

  11. Re:The perfect motivator by Anonymous+Cowrad · · Score: 2, Funny

    Homer: Sir, I need to know where I can get some business hammocks.
    Hank: Hammocks? My goodness, what an idea. Why didn't I think of that? Hammocks! Homer, there's four places. There's the Hammock Hut, that's on third.
    Homer: Uh-huh.
    Hank: There's Hammocks-R-Us, that's on third too. You got Put-Your-Butt-There?
    Homer: Mm-Hmm.
    Hank: That's on third. Swing Low, Sweet Chariot... Matter of fact, they're all in the same complex; it's the hammock complex on third.
    Homer: Oh, the hammock district.
    Hank: That's right.

    --

    --
    pants ahoy
  12. Re:Bad programmers don't change. by FlatEarther · · Score: 3, Funny
    make sure management has access to this visibility

    You've got it made. Management will surely know that you've been doing all the work - because right now you're working with your future management team. So try not to piss them off too much !

    The Earth is truly flat - it's only space that's curved

  13. Use slashdot to your advantage... by orius_khan · · Score: 5, Funny

    Block "http://www.slashdot.org" at the firewall :)

    Personally, I just complain about my co-workers on the front page of Slashdot... they all get pissed and quit, and then I can replace them with new people who know what they're doing. Seems to work....

    --
    Sometimes the best solution to morale problems is just to fire all the unhappy people.
  14. This works in movies by Faeton · · Score: 2, Funny

    You could steal their red stapler. That always seems to motivate people.

  15. Hire.... by _ph1ux_ · · Score: 4, Funny

    .... this motivational speaker for developers:

    ballmer

  16. Re:Don't motivate... by ronfar · · Score: 2, Funny
    Burns: Now, as an added incentive, the second-to-last team to arrive at the cabin will receive an hilarious "world's first employee trophy."
    Homer: Hey, this sounds like fun!
    Burns: And the last team to arrive will be fired.
    Homer: [chuckles] [realizing] Uh-oh.

    And to show that I'm not playing favorites, both Smithers and I will be participating. Who knows? I might be the unlucky one who gets fired. [sotto voce] Not bloody likely.

    -- Simpsons' episode "Mountain of Madness" direct quote from Simpson's Archive )
    --
    All the creatures will die, And all the things will be broken. That's the law of samurai. (Jubai, 1605)
  17. Show me three useless programmers.... by orthogonal · · Score: 2, Funny

    Show me three useless programmers....

    And I'll show you two testers and an aspiring manager!

  18. Re:Bad programmers don't change. by kosipov · · Score: 2, Funny

    Are you hiring?