If you have kids you’ll know how disgusting a sandbox can get. Just keep that in mind as you read this post and think about how it applies to some of the things you’ve done in a Salesforce sandbox over the years.
One thing I’m really growing tired of is dealing with half-baked tests, proof of concept examples, and random fields with no descriptions in the sandbox that I’m using to deploy changes to Production. Part of the reason for this is that prior to the Spring ’16 release Enterprise Edition orgs only got a single sandbox. So if an admin is trying something new, they only have one sandbox to work in. As of the Spring ’16 release you now get 25 with the same edition. This post is going to talk you through how to leverage one or more of those 25 to stop screwing up the sandbox you need to make real deployments from, and separate your playground from your deployments.