Re:GitLab Database Incident – Live Report
by jjirsa on Thursday February 02, 2017 @10:25AM
(#13551107)
Changing the meaning of a decades old command is the problem - du / can take hours to run on some systems, and randomly bouncing shit in prod is the type of cowboy shit that happens in a panic (see gitlab live doc).
Docs and checklists are fine, but at 2am when the jr is on call, you're asking for problems by making rm == mv
Docs and checklists are fine, but at 2am when the jr is on call, you're asking for problems by making rm == mv