Earlier quoted context omitted.
There was a thread recently about a repo that accidentally went private and lost all of its stars because of confusion with GH teams vs GH profile readme repo naming. I think this type of prompt is very useful for explicitly preventing the rare worst case scenarios but the problem is making any type of prompt "routine" so that our brains fail to process it.
The suggestion in that post about how to fix it is good, and mirrors one I read in the Rachael by the Bay blog - type the number of machines to continue: https://rachelbythebay.com/w/2020/10/26/num/ The take away by both is there is actually something to do which can wake people up when the stakes are high, and they might not be doing what they expect.
I Accidentally Deleted 7TB of Videos Before Going to Production
271–280 of 362 posts
Re: I Accidentally Deleted 7TB of Videos Before Going to Production
#272Earlier quoted context omitted.
My tip would be: read what you sign.
Just to clarify, my company is under an NDA and not personally me. It also encompasses only the actual project details so a post like this is legally compliant. (Not a lawyer, might be wrong)
If your company is under an NDA, your company will have an obligation to ensure that you also do not disclose information.
Companies are mostly just collections of people, and an NDA is mostly meant to stop people working on the project from talking about the project.
Re: I Accidentally Deleted 7TB of Videos Before Going to Production
#273Re: I Accidentally Deleted 7TB of Videos Before Going to Production
#274Re: I Accidentally Deleted 7TB of Videos Before Going to Production
#275Earlier quoted context omitted.
I love ZFS too but that's not really relevant to this discussion because the deleted items were on a video hosting platform and the company did already have local copies.
Yes and? Make a snapshot on live. Again, never touch data before snapshot.
There are a hundred ways this problem could have been prevented but ZFS isn’t one of them.
Re: I Accidentally Deleted 7TB of Videos Before Going to Production
#276Earlier quoted context omitted.
Rather than commenting it out, I suggest adding a --live-run flag to scripts and checking the output of --live-run=false (or omitted) before you run it "live."
But then you have double the chances of introducing a bug for the specific scenario we are talking about: Before: there is chance there is a bug in my "delete" use case Now: what we have before plus the change that there is a bug in my "--live-run" flag
Re: I Accidentally Deleted 7TB of Videos Before Going to Production
#277The root of this particular issue was Vimeo's failure to do this migration for their customers. Vimeo OTT has a codebase written in Rails, whereas the main PHP application is written in PHP. At the time Vimeo acquired Vimeo OTT's codebase, the Vimeo OTT codebase was small — around 10,000 lines of Ruby. Rewriting that codebase inside the Vimeo PHP application would have been a tough technical challenge for the all-Rub…
Re: I Accidentally Deleted 7TB of Videos Before Going to Production
#278Re: I Accidentally Deleted 7TB of Videos Before Going to Production
#279Aaaahhh, the feeling you get when you notice that you fucked up. Everything gets quiet, body motion stops, cheeks get hot, heart starts to beat and sinks really low, "fuck, fuck, fuck, fuck, fuck, fuck, fuck, fuck, fuck, fucking shit". Pause. Wait. Think. "Backups, what do I have, how hard will it be to recover? What is lost?". Later you get up and walk in circles, fingers rolling the beard, building the plan in the…
Pffft, it's not a real panic until you weigh the pros and cons of leaving the country with nothing but the clothes on your back and becoming a illegal immigrant shepherd in a nation with too many consonants in its name. (Your description is so, so, spot on.)
Re: I Accidentally Deleted 7TB of Videos Before Going to Production
#280Spoiler:
But there was a backup that could be reuploaded in time and everything was fine in the end.