"The implication: only bad coders need code reviews."

'Good programmers' is most likely used in the relative sense as in "I think they are good programmers", which implies that Ken's views of coding is in sync with his co-workers. If everyone is on the same page, using the same style, and the same conventions then a code review is essentially just a way to put a formal process over a discussion about how each problem is solved. If that communication is happening informally (as it sometimes does with programmers who like talking about their work), then a formal process is redundant.

If there are a bunch of programmers with very different views of what they are doing, it in no way implies that they are bad at it. They just have different ways of working and different experiences. In that case a code review would be hugely beneficial because it pushes them to learn from each other and consolidate their views.

Paul.