What makes you feel Moose pushes strongly toward bad class design?

:) tye say the documentation and implementation

The documentation (esp examples) encourage designing classes in terms of attributes not in terms of interfaces (tye say good design is interface first, then internal details like attributes)

The implementation , is based around attributes, so if you don't generate accessors then you can't make use of many "roles".

see How Large Does Your Project Have To Be to Justify Using Moose?, read tye say this