Gavin Sinclair wrote:
>
> My favourite refactoring pattern at the moment is to move all the related
> private methods of a class into their own class.  It helps to clarify the
> real responsibility of the original class, to highlight the relationship
> between them, and to test the supporting code more easily.  (The difficult
> part is thinking of a name for the new class.)

I hadn't thought of this, but it is immediately obvious to me that this can
be very useful. I'm going to  try this on the Java project I'm doing for
work!

Thanks,
Curt