I am also a software engineer, to be exact.

I did a shameful and dangerous thing today. The cause is that there is an old customer has been using the system for seven or eight years, the recent database appears a large log file, the normal operation can not achieve log slim, can only stop business after deleting the log and re-attached to the database. I didn't operate it before. I thought I could finish it in two hours at noon, but in fact, there were too many problems in the middle. Finally, I stopped working for an hour before returning to normal, it's a mess and it's a bad influence.

在那一个小时我真真切切的感受到了巨大的压力。一方面来自客户的抱怨，一方面担心数据无法正常还原，当时的感觉真是如坐针毡，就像热锅上的蚂蚁。还好最后有惊无险的把数据库给还原上去了。

After this incident, I found some problems of my own, which ultimately led to today's accident.

To sum up, there are a few points

1. Blind confidence in the operations that they have not carried out, and do not think about the various problems that may occur in the middle.In this regard, I should test the entire operation process in advance, and then operate on the official data after it is completely passed.

2. Lack of systematic contingency planning, failure to anticipate consequences in advance, and failure to restore data in advance if the objective can not be achieved.

3. The most important thing should be not to delay the customer's normal use as the premise to complete these tasks.

4.遇到这种紧急的事情，不能慌乱，要保持冷静，想办法解决问题，而不是干着急。

So my title today is“Don't fight the battle without preparation”, do something to be responsible for the consequences. After this incident, although there is still lingering fear, but I believe that the next time will be done well.

Go, go, go, go, go, go, go, go, go, go, go, go, go, go, go, go, go, go, go, go, go, go, go, go, go, go, go, go, go, go, go, go, go, go, go,