I was a data analyst working at a company where all the data was in a Django-mamaged database. Not once was I confused by the table or column naming. I was ki

I was a data analyst working at a company where all the data was in a Django-mamaged database. Not once was I confused by the table or column naming. I was kind of annoyed by all the long table names and all the joins I had to write out, but it was all fairly tidy and organized, and I almost prefer it to the human-designed databases I've worked with. Theoretically yes if they one day renamed the app then there would be some legacy names in the table. Who cares, shit happens. Regarding read-only access: we were a small enough organization that I actually did have full access to the prod database. I hated having it and tried to work off of our "QA" clone whenever possible, or made my own local timestamped copy of the prod data.