This article speaks about one of the many, many reasons I don't like Robert Martin's approach to programming. If some principle results in a handful of single-method classes that don't really do anything on their own, the principle is not a good basis for design.
I find the author's alternative much more useful in practice.
I find the author's alternative much more useful in practice.