I feel like slow CI can definitely be a huge bottleneck in large projects, with lots of tests. If you are making changes that affect lots of different areas, th

I feel like slow CI can definitely be a huge bottleneck in large projects, with lots of tests. If you are making changes that affect lots of different areas, there are likely too many tests to run locally, so some test failures will only be caught by CI. Slow CI makes it take far longer to iterate and solve these failures, and forces you to multitask more while waiting for CI to finish, and context switch whenever you have a failure. I think that, if slow CI is a big problem, it probably indicates that your codebase is too tightly coupled, and you aren't testing the right things. But it is still a problem.