Comments on: Creating Good Software Development Teams

By: richtaur

richtaur — Thu, 01 Jul 2010 22:33:42 +0000

I think bad programmers are particularly difficult to spot, partly because of the Dunning–Kruger effect: http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect

By: Doolwind

Doolwind — Tue, 06 Jan 2009 23:56:30 +0000

Thanks Dean, I’m glad you agreed with my thoughts. I should have a follow up to the post soon as I’ve come up with a number of new ideas.

By: Dean Longmore

Dean Longmore — Tue, 06 Jan 2009 23:53:52 +0000

This comment isn’t specific to this post, but I must say you really know your stuff, we certainly have some talented people in Brisbane.

By: Daniel

Daniel — Mon, 16 Jun 2008 05:30:40 +0000

You seem to be a specialist in common sense posts A pity there is not much common sense spread around evenly in the world. I will browse your site more now since I discovered it.

By: cowlibob

cowlibob — Fri, 25 Apr 2008 14:39:51 +0000

You can be fooled by experience, but that’s what a probation period is for. People going bad after that time is a different story. I believe that firing them is the last resort though [but sometimes the only choice]. It’s the responsibility of the leader(s) and the whole team to bring this person back into line.

When we have someone in department that is slacking, I let everyone else in the department know. And then we encourage this person to work hard. Not by telling the person, but by paying attention and helping them and giving them moral support and assistance. This usually solves most problems. If a programmer continues to be a bad apple then you move up to the HR department and try and resolve the problem.

for me, more than a bonus I want the feeling of satisfaction for completing a great project and achieving it with your co-workers. That’s what a team is all about. Attach that to Doolwind’s ideas of how a business should treat staff and you have a great team who will make and deliver a great project.

By: Doolwind

Doolwind — Fri, 25 Apr 2008 10:20:06 +0000

cowlibob-

Very true! Prevention is better than cure. I’ll update the title of that section to better fit what I mean.

By: Drealmer

Drealmer — Fri, 25 Apr 2008 06:57:10 +0000

Experience is only part of the equation. The goal of a job interview is to look beyond to check the fundamental skills Doolwind listed in his “Qualities of a good programmer” article. As of “who let the jackass through the door”, I’d say it’s more complicated than it sounds. First, you can hire a good programmer that will turn bad a few years later (then you might have to ask yourself if you don’t have your share of responsibility for letting that happen), you can also be fooled by experience (“this guy worked on xyz, he must be good”), and finally there are times where you just need manpower: right here, right now, and you don’t have time to pick the cream of the crop. I agree that this last point is usually a bad idea, but let’s face it: that happens.

By: cowlibob

cowlibob — Fri, 25 Apr 2008 05:00:36 +0000

I noticed you didn’t mention anything about actually not hiring bad programmers in the first place. Who let the jackass through the door?

By: Doolwind

Doolwind — Fri, 25 Apr 2008 03:37:29 +0000

Mig-

Perhaps I should have been a little more specific with what I class as a “bad programmer”. By bad programmer I don’t mean inexperienced programmer, nor a programmer that makes mistakes. For an in-depth explanation of a “good programmer” see my blog post here.

Basically if someone is in a position they are not experienced enough to be in, or are simply slacking off then they need to be removed from the position. I could have said that they should be demoted to the position that suits them, but realistically, I don’t think this works. If a programmer is struggling, but is willing to learn and become better, then they are no longer classed as a ‘bad programmer’ and the team should work together to help this person reach their potential.

A lot of the issue comes from programmers that are too proud to turn down a position they are under qualified for. All of the very best programmers I know have been offered positions beyond their ability and have turned them down. I see bad programmers being the ones that take on responsibility when they know they can’t fulfill the role, simply to get more money or power.

By: Mig

Mig — Fri, 25 Apr 2008 03:17:18 +0000

Just wanted to ask a question regarding #1… This is coming from an unexperienced game programmer in the making.

Any thoughts on helping the programmer out before letting him go? Of course he would have to be cooperative and the company have the resources available, but I don’t see why we would have to get rid of any position so as their work improves and attitude is right. If they don’t want to be “helped” then I can see why.