That's fair criticism -- I've updated the article to make it a bit more clear. The point isn't to create "NounVerber" classes as a solution for everything, but

That's fair criticism -- I've updated the article to make it a bit more clear. The point isn't to create "NounVerber" classes as a solution for everything, but to break your objects apart according to the roles that they play in solving the problem. Thinking of objects as actors has helped me with this over the years. In the example "ProductSearcher" should probably have been named "ProductSearch" -- you can instantiate it, pass it around, and so on, so it doesn't quite behave like many the "NounVerber" objects in Javaland (e.g., AbstractFactoryBeanBuilderImpl). When you couple this with a functional approach -- where you separate transformation and state -- magic happens. But that's a future article. :)