• Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

Pair Programming

What kind of 'pair programming' is this?

Sounds more like you're the senior and you need to train this novice.

If they're not up to the task, and not being able to get SVN running after a few weeks I'd suggest IT is not a career they should aspire too, I'd go to the manager and tell them this guy needs replacing.

If you don't, you will get the blame for the failure.
 
How can someone be good but not able to use SVN? Any developer NOT using source control as standard, or thinking it's an optional extra, has serious deficiencies.
 
How can someone be good but not able to use SVN? Any developer NOT using source control as standard, or thinking it's an optional extra, has serious deficiencies.

:eyes
 
How can someone be good but not able to use SVN? Any developer NOT using source control as standard, or thinking it's an optional extra, has serious deficiencies.

I think it's more of a case of doing it on his own for the glory. The SVN is a nice reason to keep working on his own.

Only five and a bit weeks left of the current contract left anyway, subject to possible extension. The locations is great, but the project isn't the best. Still we can't have it all, eh!
 
It'd be a shame if his PC got kicked over by mistake...
 
Odd how things can come together. The team leader just came over so I just said that we had to ensure that all the code is being checked in. As if by magic the 'other half' appeared moments later so I've agreed to stay late to help get a working version of the code checked in.

I do find this kind of manoeuvring somewhat distasteful, but I guess it's a part of working. Still all seems okay and no bad feeling.

I would check his code in as is, and commet it as his code. Then check it out or branch it, before making any changes to get it working. Because if there is any problems, you are bound to here the phrase "It was working for me" :suicide:
 
I would check his code in as is, and commet it as his code. Then check it out or branch it, before making any changes to get it working. Because if there is any problems, you are bound to here the phrase "It was working for me" :suicide:

I intend to go one better. I'm going to sit with him while he checks in his working version (when it works). I'd rather have a basic working version than a fancy, 'nearly working' version.
 
I think it's more of a case of doing it on his own for the glory. The SVN is a nice reason to keep working on his own.

Only five and a bit weeks left of the current contract left anyway, subject to possible extension. The locations is great, but the project isn't the best. Still we can't have it all, eh!

A person who will only / can only code on their own is also not suitable for a career in IT.

Code is a method of telling another programmer what you intend the computer to do. If they're incapable of this then their code is worthless.
 

Advertisers

Back
Top