4 ms·
What is the point of having a human "database operator" who carries out simple tasks like deleting an index when it shows up in a work request log? Is this how
by leeleelee 11y ago
What is the point of having a human "database operator" who carries out simple tasks like deleting an index when it shows up in a work request log? Is this how most companies structure their dev teams?
If you have a human there to perform tasks, then it would seem natural to allow them "human advantages" such as the ability to communicate with the person who created the request, or the ability to have some of their own checks and balances before performing the index deletion (ex. let's take a look and see if this seems safe based on the current schema and codebase).
I am also surprised how easy it was for a single dev to make a request that subsequently results in the modification of a production database.
- thrownaway2424 11y agoIndeed, what is the point? If they have some separation of concerns between dev and ops then it also makes sense to give ops some separate rights and responsibilities, such as vetting a change like this by analyzing the resulting query plans from a sample of production database queries. I'm sure something like that will be in their internal postmortem action items under "prevention".