> but at the time the code seemed completely correct to me I venture this kind of (misplaced) over-confidence is not atypical of many junior developers. As som

> but at the time the code seemed completely correct to me I venture this kind of (misplaced) over-confidence is not atypical of many junior developers. As someone with a few years under my belt, I don't care how sure I was of the code I wrote that deletes important data, I would have gone through the code over and over again, and at least ran a simulation (by maybe logging the generated delete urls for manual verification). It's a rite of passage and we all went through something like this. It's how you learn and grow. >It also should probably teach something to Vimeo No. Even if Vimeo could have made things better, it's still your fault. You have to take responsibility for your business. At the end of the day, if this causes the closure of your company, Vimeo is still fine.