I just thought of a second, more likely problem. An error in the development database could cause consumption of resources that would impact other databases. Also, there's the danger of the developer connecting to production instead of development and really hosing things up.

So, this does sound like a bad idea, but I'd still like to hear thoughts on the possibility of taking the whole server offline, as suggested, if something goes wrong in the development database.