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"