Code readings: Crockford's approach for building strong software teams

Would pair programming with frequent pair rotations be better than Code Readings? It seems you get all of the value of Code Readings, but throughout the entire process.