I disagree with this. For one thing, cyclomatic complexity has a specific meaning, and the one you gave ain't it. Cyclomatic complexity is actually the number of loops code takes through one or more data sets. So if you have a data set of N elements and another data set of N elements, and you have an outer loop that does some operation on N and an inner loop that does an operation on M, then the O is M*N. If you have a loop through N that compares N to itself using an outer loop through N and then an inner loop through N, the O in N^2. Etc.

Your absolute _best_ chance at clean code is on a team of one--if that one person has a great understanding of the fundamentals, the code will be clean. The more people you add to the team, the less clean the code will be, because not only do most people have an imperfect understanding of clean code, it's a political minefield trying to get people who don't understand clean code to try to write it. The more people, the worse that is.