I found this short post on pair programming which sums up many of my own experiences. Pair programming is one of my favorite tools, but it does require you to be aware of any potential problems. As in the article it is important to realize when it not suitable, and to remember to take regular brakes so the programmers can unwind and catch up on e-mails etc. Unscheduled meetings can also be a problem if one of the programmers constantly gets pulled away.
When I first read Domain Driven Design the role of a Repository was one of the things that were a bit hard to grasp. I really don’t think I have a clear vision of it still, but Fabio Kung has a post that clarifies some of the questions. It was written as a response to a post by Gavin King that sparked quite a lot of debate.
Ted Neward has a good article that touches on many things, but the main message is really that we all write shitty code and we need all the help we can get in making it correct. That includes TDD and other tools to test and analyze our code.
It’s a good read as always, check it out.