Jeff Langr and Tim Ottinger have written an article where they share the benefits they have seen in their experience with pair programming. They also have put together a slide deck on rules that pertain to this practice.
If you are new to pair programming, or have not heard about it, is the practice where two developers sit at one workstation. One assumes the role of the driver by writing the code, and the other assumes the role of navigator (or observer) and resviews the code as it is written. The roles switched frequently so there is no set role for each developer. More info can be found
The other day I ran into the html5please.us which is a site that offers expert advice on which features to use and not to use when developing apps. The site breaks its advice down into three categories: use, use with caution, and avoid. Scroll all the way to the bottom of the main page and you’ll find the list of contributors. Divya Manian, Web opener for Opera Software; Paul Irish, developer programs engineer on the Google Chrome team; Tim Branyen, a software engineer at Bocoup; Connor Montgomery, a Web developer and computer science student at St. Louis University; and a host of others. This slide show takes a look at the HTML5 and CSS3 elements that HTML5 Please says are completely safe for developers to use.
In object-oriented programming, mock objects are simulated objects that mimic the behavior of real objects in controlled ways. A programmer typically creates a mock object to test the behavior of some other object, in much the same way that a car designer uses a crash test dummy to simulate the dynamic behavior of a human in vehicle impacts. This is something that you will run into if you embark in the journey that TDD is. This article The Art of Mocking gives you a very simple and high overview of this technique. There are a number of frameworks out there that will help you with the creation of objects and their consumption.