Tuesday, January 27, 2009

Pairing and Code Quality

A simple reminder...

We are pretty much a pair programming shop...although we have one project that started with a single person and has evolved to be a fairly complicated piece of code.

The developer on the project is very talented but we don't have the same level of testing rigor woven into the rhythm of that project as it in our core development effort. As a result we are seeing late breaking defects that are easy to fix, but annoying to our client.

The fix is going to be bringing that project into our main effort and ensuring that someone is always pairing when work is done on either.

No comments: