4 ms·
I was thinking the same thing. If nothing else, I don't understand the role of "database operator" if they'll just blindly delete a critical index without thin
by jlarocco 11y ago
I was thinking the same thing.
If nothing else, I don't understand the role of "database operator" if they'll just blindly delete a critical index without thinking about it. Shouldn't that person have known better than anybody how critical the index was?
- gms 11y agoThere is an open secret you may not be aware of: every startup is a shitshow on the inside.
- fein 11y agoJust startups? It's just as hilarious in corporate America.
- xacaxulu 11y agoAlso top 20 financial institutions, USG orgs and places that store your healthcare and tax information ;-) I'd argue that a good number of startups these days (especially ones borne out of larger organizations with lots of combined experience) are way more capable of handling these issues with finesse and speed.
- perlgeek 11y agoThere are different levels at which you can operate a database. One is to keep it running, monitor disc space, response times etc. but otherwise leave the schema to the developers. Or you can own the schema, discuss all the changes and migrations with the developers etc. If it was the first kind of DB operation (which wouldn't surprise me, because that's what our $work has as well), it's not surprising that they trust the developers to provide sane DDL patches.
- jlarocco 11y agoOkay, I've never seen the first kind of DB op. The places I've worked with dedicated DB people were a combination of the first and second types you listed. That situation would explain the Stripe outage, though. TBH, it seems odd to call the first one a "database operator" instead of an IT admin.