This is something I’ve taken with my in my career myself, and in my experience it fosters a much healthier culture than firing someone for dropping a database they frankly should not have had the rights to drop in the first place. Like… what organisation in all seriousness gives a junior developer the access rights to drop a production database on their first day? And then after this even has the audacity to blame the junior dev? Seriously…
It is pretty normal. Someone with university education, should know how to use a SQL client! I personally would fire such person as well. Carelessly copy&paste and execute code from some website is a huge redflag! Getting rid of such person on their trial period is very cheap....
Also many services are not mission critical. DB drop could mean short downtime, and restoration from backup (or Kafka stream), and with little loss revenue.
But I expect people to take lot of care and thought when doing something in production like Database. And some even in shared development/pre-prod one. If you know how to replicate whole thing, go wild you are only wasting some time.