Welcome to the community!
If possible, don’t let people get creator access to an important base unless they really need it and you can verify that they really know what they are doing. I think that every base should have at least two people with creator access (for backup purposes).
I like to give people creator access to a sandbox base or a playground base where they can test things out and see how things work, make mistakes, and recover in a safe environment. I also demonstrate how small changes can break systems and share stories of the headaches involved in recovering from accidental changes. I also encourage everyone to use a “personal sandbox view” for one-off creator-type activities. Then the changes are copied over to production views only after everything is tested.
I also use On2Air schemas to back up my schemas of important bases. I also periodically duplicate bases to have an easy way to look at old configurations.
I lock views that should not be messed with. I try to avoid triggering automations off of views and embed the conditions in the automation itself.
I also really like the Enterprise feature that shows the dependencies of a field and teach people to use that before making any changes to a field.
I try to design my Make integrations so that scenarios are not tied to a specific base but can work with any base that calls the webhook. This also makes testing the integration prior to putting it in production easier.