New developer drop the production database. Thank god the daily backup was made only couple hours before. 3 developers spent the rest of the day recovering the lost data

I was talking about that with a friend, and I think that those kind of situations are more procedure mistakes. I mean, the new developer MUST NOT be able to perform that, unless some other experienced guy aproves his code.

Hmmm... What about compliance?
In Germany there is an independent agency which visits different companies from time to time to check whether anyone has the opportunity to access used databases directly for manipulation.
Of course not the agency itself, but the workers of this agency are visiting.

So there is a requirement, that every information must processed via an ui and by a user who has sufficient rights.

This developer is not new new, he already working part time with us for quite sometime, and just started working fulltime yesterday

I then create a new database user that don't have privilege to drop the database. Should have done that earlier, I guess we just don't put much concern to it before as we are small team startup that just have too much task to work on