I once deleted all the virtual phone numbers in the municipality where I was working. It wasn’t entirely my fault as I was basically working with some Cisco tech that nobody knew how worked doing pretty much exactly what our IT operations department had requested, but it was still me who did it. I went to tell the CTO feeling more than a little afraid. I didn’t coat it in the “it wasn’t my fault” part that I did here, because I didn’t really think it mattered, and it turned out that it didn’t. He basically told me that while he wasn’t happy that it had happened, he was happy my first reaction was to come running and admit my mistake so that it could be fixed, and that everyone makes mistakes but it’s the ones who hide it that are dangerous.<p>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…