What do you like best?
I can use Rudder to break the communication barriers I normally have to deal with in IT.
Normally, there's "the technical stuff" and "the stuff management needs". Both are distractions from each other and fixing one doesn't solve the other at all.
With Rudder I can easily show non-admins what's working, what we need to do, and they can digest that information to a complete understanding. Project managers, bosses and beginners can understand what's happening.
What do you dislike?
I would like it to be easier to file away what I built, in a sanitized version. I hope for more interfaces to other tools (i.e. there's an ansible plugin, I would love to use that as an an exporter so I don't have to ever build ansible code again).
It is also a bit "too much" for very small setups.
Recommendations to others considering the product
Set it up, and slowly start doing what you always wanted to do (i.e. have a really great .bash_profile).
Keep in mind, since this is agent-based it is almost impossible (never say never) to lock yourself out.
What business problems are you solving with the product? What benefits have you realized?
Built some very flexible infrastructures that adapt well no matter where deployed.
Ensure things aren't just provisioned, but kept OK all the time.
Allow people to easily change what they need in a place they understand.
Gather year-long statistics on system maintenance needs, and as such, be able to tell when everything is tidy, or how far we have move from that point. I am dumping that data into Nagios (Check_MK to be specific, and also into ElasticSearch. My dream is to have this full circle - I'm also collecting other data, including IPFIX metrix into the same ElasticSearch instance, and am just waiting for DARPA to come up with some cool aggregation technique for all-different data :-)