in reply to (OT) Motivating the Unmotivated Programmer

Sounds to me you need both carrot and stick. What he needs is a project that his clearly his in the eyes of his peers, has tangible objectives, and a deadline that is tight. The probability of success should be low (The first time around). At that point you should have his attention and it should be fairly obvious to him and the employer where his skills most need improvement and courses should be offered to him to improve those areas.

Upon completion, rinse and repeat as necessary. Any nice guy that isn't motiviated by that cycle of opportunity and challenge, deters from the success of a team, and needs some unemployment therapy in order to get his priorities straight.

coreolyn
  • Comment on Re: (OT) Motivating the Unmotivated Programmer

Replies are listed 'Best First'.
Re: Re: (OT) Motivating the Unmotivated Programmer
by little (Curate) on Jan 16, 2002 at 17:48 UTC
    I'd go for this as well, but would like to add: "make him need to work with his collegues to accomplish the project". As in this way "code review" is naturally supported by all team members, and it will show clearly the need to stick to coding conventions, modularization and open ones eyes for security issues as the other programmers don't want anyone to plug security holes in the code to which they provided secure scripts/ modules to.
    0.02

    Have a nice day
    All decision is left to your taste
Re: Re: (OT) Motivating the Unmotivated Programmer
by Fengor (Pilgrim) on Jan 17, 2002 at 15:17 UTC
    I fully agree with coreolyn. After what i read in Ovid's description this guy needs the stick to get going but if he's going then put the stick away and the carrots out...
    I know the situation very well from myself (i have to admit, that i tend to be the same type of lazy programmer). As long as I'm not under pressure / dead line I tend to put things up till I have to absolutely do them now.

    My tips for you are:

    • Keep him focused! - Don't let him put up things. When it's out of sight he'll forget about them
    • Give him interesting problems to solve - If he's like me he will surely take the bait. So give him a problem that absolutely requires something his code lacks of (e.g. data validation)
    • Give him feedback - Either good or bad it doesn't matter cause nothing is duler than work for which you won't get a feedback
    Hope this helps you a bit

    --
    "May you live in Interesting Times"
    -- Terry Pratchett, "Reaper Man"