Like everything the author listed it's about execution and applying the right tools to the right job. Some places _only_ do pair programming, some places go so

Like everything the author listed it's about execution and applying the right tools to the right job. Some places _only_ do pair programming, some places go so wild with their unit tests that it becomes incredibly unwieldy, and lots of times different approaches get cargo culted from organizations where it made sense (we're a 10,000 member team writing a new OS) to a one where it doesn't (we're 2 people making a CRUD app side-project that got a little traction).