coupling, complexity, and cohesion

I forgot to mention it here, but Scott Bellware mentioned that coupling, complexity, and cohesion are the fail points where shortcuts cause problems when I saw him speak Monday evening. Having a good understanding of coupling and complexity, I asked for a definition of cohesion and was told that cohesion would be poor in situations when a class has gunk in it that it does not really need. Violations of the Single Responsibility Principle are of poor cohesion and a common code smell manifests in classes having stuff in them that is seldom used and rarely appears in tests. Such extra weight should be teased out into supporting classes.