It's common practice to run tools to calculate complexity as a CI (continuous integration) task. For example, at the company I work for, we check code complexi

It's common practice to run tools to calculate complexity as a CI (continuous integration) task. For example, at the company I work for, we check code complexity every time someone pushes to certain branches in our repositories, and mark the build as unstable if the score is too high. In that case, the only acceptable solution is refactoring; all builds must be stable before the task associated with the change can be considered complete. It's not reasonable to run it once a month or longer---by then we've moved on, context and focus have been lost, and refactoring is considerably more expensive (both for development and because it has to go back through QA) than if it were done immediately.