Hacker Newsnew | comments | show | ask | jobs | submit login

The author makes mention of using a UI to connect to their db. If i was in a position over there i can see myself writing a script to clear out the tables i wanted. This reduces errors, but not the risk.



And yet, the net result is the same; right-click, clear table, or ./clearTable.sh. Both are human actions, and both are fallible. What if some prankster edited clearTable.sh to do the users table instead of the raids table? What if he did it himself to test something?

-----


Forget a prankster! What happens if the full RAID array fails that holds the database? No backups: dead company.

-----


Heck when you put it that way, this guy actually did them a FAVOR. He ONLY wiped out the User table. The company was able to learn the value of backups, and they had enough data left to be able to partially recover it from the remaining tables, which is much better than the worst case scenario.

-----


Do you think the company learned the value of backups, or do you think they learned to blame junior devs for fuckups? Sounds like they learned nothing, because no attempt was made to determine the root cause.

-----


Arrow up, enter Or ctrl+r <something> enter Can be very dangerous if something other than your routine is in the bash history.

-----


Exactly. It's not like nothing bad ever happened from the command line ;-)

rm * .doc

-----




Guidelines | FAQ | Support | API | Lists | Bookmarklet | DMCA | Y Combinator | Apply | Contact

Search: