Code Smell

Although I've used Moo before and I'll undoubtedly use it again, I think it's still safe to say that the use of Moo is usually a sign that you may have problems in your code and/or your architecture. Moo might be the best (most cost-effective, most palatable, etc.) solution to your problem, but I do suggest you sit back and take some time to ask yourself, "Why do I need to copy values from one set of objects to another set of objects?" "Do I really need parallel hierarchies?" "What problem am I solving, why do I have it, and is there a better way to go about it?"

If Moo helps you, then I'm glad. I just don't want it to enable you to do terrible things without warning you that you there might be a better way.