Nah. I've done a startup where we did TDD and pair programming (with frequent pair rotation) for all production code. We were incredibly productive. High code quality and good tests mean you get to spend way less time on mysteries and bugs. Aggressively refactoring the system means you end up with flexible, composable units that make it easier to keep up with rapid changes.
It's basically the same deal as cooking. Can I go faster if I dirty all the pans and don't worry about cleaning up? For a little while! And after that, productivity and quality drop. There's a reason that professional chefs are big on "working clean". For those interested, there's a book with a lot good interviews with chefs on their work practices. I think a lot of it translates to software: https://www.workclean.com/
It's basically the same deal as cooking. Can I go faster if I dirty all the pans and don't worry about cleaning up? For a little while! And after that, productivity and quality drop. There's a reason that professional chefs are big on "working clean". For those interested, there's a book with a lot good interviews with chefs on their work practices. I think a lot of it translates to software: https://www.workclean.com/