Thanks! The example used case you describe for `thinker sync` is certainly a good one for smaller dev shops - unfortunately many larger enterprises might have issues with cloning production customer/user data for development purposes. Of course I don't expect this to apply in every situation.

One more thing that you might want to clarify: you gave a metric for the time it takes to sync to your local database over the internet. I think it would be a good idea to indicate the connection bandwidth and the amount of data which was actually saved from being transferred (perhaps only in number or percentage of records) as well as post the full time of a regular clone as a base metric.