Whoops, the deleted GP was mine. (I sometimes delete things when on second thought they seem pointless. But not if there are replies.) What I said was that if you need a library to tell you which functions have too many arguments, which classes have too many methods, etc., then you've already lost the battle against complexity. These things should be taken care of while they're still obvious by inspection. Which incidentally reveals a certain irony in the library's name (it means "briefly" in Russian).
I haven't read the main article yet, so forgive me if I've missed the point.
But I take issue with the "if you need a library to tell you [...], then you've already lost the battle" bit. You don't always get to create your codebase - sometimes you inherit something, and need to carry it forward. In a past life, most of my work was diving into ancient, undocumented, unfamiliar codebases and doing what had to be done. I'd love to have had tools to take some of the pressure off.
Just because you don't need a screwdriver, doesn't mean I need to make do without one.
