Nice Guy, but he can't program a damn...
I'm currently in the process of working with a so-called more experienced programmer on an asp.net project. Small, custom app mind you - and he's a complete disaster. He forgets to check-in his code and eventually winds up losing some of his code. He also apparently has trouble following a simple req. spec that he helped author (all of 1 page.) He's been trying to get his boss to put him on a .NET project, and obviously he's succeeded. He's in general, incompetent and I want to tell the boss(es) to put him elsewhere (we're a consulting shop,) but I feel bad because he's a nice guy...*Sigh* Unfortunately this also means, I'll be here later tonight than already planned. Has anyone been in a similar situation? Suggestions?
Are you managing this guy or just working with him? If you are managing him that I would cal him him, give a specific task to do in a specific time and make it clear that there would be consequences if he does not do it.
"Has anyone been in a similar situation?"
I defer to the infinite wisdom of Joel on this topic:
There's not enough code to send him on his way...they wanted to speed up this project's development by bringing him on. Should buy them all a copy of The Mythical Man Month... I don't manage him per se, but I know more about the project from a technical standpoint than anyone else. Instead of helping speed things up, he's slowing things down...this creates a problem when release time comes (end of next week.) He can't even create a simple SQL script to manipulate a database schema...how does he expect us to put this in production??! Argh...
> when release time comes (end of next week)
If you let him do all the interfacing with other people, he may end up as your boss. It's not really your work writing code that makes an impression on the people around you. You could end up doing all of the good work, and he will get all the credit for doing to talking.
One Programmer's Opinion
Keith Wright and One Programmer's Opinion have nailed this one, I think.
Must be a Manager
He can't program worth a damn in general. A 9 to 5'er who doesn't care about becoming 'good' at what he does, he just wants to play with the cool toys. I've been interfacing with the users/customers and delegating the tasks to him (which he's completed in a half-assed manner.) Officially I'm not managing him, but for all intents & purposes I am... He's not being trained to replace me, he was thrown into the mix to try to get this project done before the deadline. If he were half-way competent, it would have been possible. In the meantime he's managed to screw up his VS.NET/IIS/VSS install and wasting more time today...
He sounds like definite management material to me.
Must be a Manager
Swap him with another team for additional hardware.
Fog Creek Home