> If it is an internal project it's even better because the cost of a bug tends to be lower than public projects.

By this, do you mean that trunk-based development with pairing has a higher rate of shipping defects to production than other approaches?

If so -- what's the upside of this approach?