# Developer Mode **URL:** \ **Category:** Ask for Help\ **Created:** [February 7, 2020, 9:12pm UTC](https://community.glideapps.com/t/developer-mode/4379 "2020-02-07T21:12:41Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\ **Post date:** [February 8, 2020, 1:18pm UTC](https://community.glideapps.com/t/developer-mode/4379/4 "2020-02-08T13:18:37Z")
The main problem with this is the direct connection to a sheet. I’m sure it’s relatively easy to have a development copy or mode, but you have to be careful if you start making structure changes to the sheet and the user has to be made well aware that they need to be extra careful when making sheet changes. The Glide team is aware of this and most likely working on a solution, but have a lot of different scenarios to consider. I’m guessing this would be a considerable rewrite of their system logic. They’re only a year old. They’ll have it in due time. They have a lot of feature requests to work through with a small team. > [@Maintenance Mode](https://community.glideapps.com/t/maintenance-mode/3758/15): > > I think maintaining the integrity of the database is always going to be an issue with major code changes. Where I work, we have different environments for development, testing, and production, so code and database layout changes move together between environments. For production releases, we have the users stay off the system. If they stay on, it’s at their own risk of being booted or having data lost. Usually the database is pretty set in stone, so changes to the database are few and far be… --- _[View the full topic](https://community.glideapps.com/t/developer-mode/4379)._