Come what may and hell to pay

2) any vegetable is better than no vegetable

Ideally you should use something like an Object Capability model, but even basic rules like "you require the Special Key that we only deploy on production systems to even access the production database" and "our git repository doesn't allow anyone to push anything that deletes history on main unless they have the CTO's ssh key" go a very long way towards preventing this from happening by accident.

If you are currently at a company where you could delete the production database without at least having to do something that involves typing "I am forcing this run right now without oversight and if it breaks anything I will get turbo-fired" you should find out who you can yell at about it.

So from then on whenever one of us called something problematic, he would make us talk it out until we could name the “bad” thing we were hinting at. In this particular class, 7/10 it was some type of oppression, and the remainder was like, “I’m uncomfortable because this is very new/confusing/pushing boundaries that made me feel safe.”

Once we stopped calling things “problematic” and stopping at that, class got way more interesting and... we all had to say, like, “that’s racist” or “that’s misogynistic” or “ew capitalism gross” out loud, which a lot of us had never done in a classroom before. Or we had to be like, “Uhhh... I’m not sure what’s so bad?” and confront our own beliefs and that was maybe even more useful.