Riding the wind of rebirth

Chapter 1199 Meeting Old Ghost
One thousand five hundred and twenty nine chapters

Zhou Zhi had finally learned the ability of officials in the system to talk endlessly, as well as the ability to paint a bigger picture.

But it cannot be said that what Long Bureau said is unreasonable. After mastering this system, future iteration work, at least in the preparation of demand documents, those working in various departments opposite you will definitely be transferred to higher-level units. Serving as the backbone, many have a greater chance of remaining on a larger stage.

If he hadn't been reborn, he would probably have experienced what the young workers across from him were going through now. Zhou Zhi couldn't help but smile as he thought about it. He almost didn't listen to what Long Bureau said.

"Now let's ask Mr. Zhou from Clover Company to talk to us about the next work plan." After Director Long finished speaking, Dad continued to preside over the meeting process, but when he said the word "Mr. Zhou", his face changed. It is inevitable that there will be a strange look on his face.

Even in my father's most bizarre dreams, he never imagined that his son would one day sit across from him and make a speech on behalf of Party B.

"Dear Bureau Long, Bureau Zhou, comrades." Zhou Zhi was still laughing at Director Long just now. In fact, he himself is already an experienced reportr: "Director Long's speech just now only praised us. There is not a word of criticism, but it makes us feel uneasy - giving us such high praise is like a mouse on the lampstand, unable to get up or down."

Everyone here laughed. Mr. Zhou was really young, but he started speaking very tactfully.

"As the saying goes, a person who travels a hundred miles can only travel half a mile. This sentence is really appropriate for our system project." Zhou Zhi said: "From the perspective of the completion of the project plan, we have completed 80.00% of it. Currently, the only work left is data initialization, parameter adjustment, joint debugging and testing, and business training, and then it will be officially put into production."

"We have made great preparations for data initialization and parameter adjustment. During the development process, we introduced real data for module writing. Although this approach is slightly illegal, it greatly speeds up the development progress. Data sorting and parameter definition are also being completed at the same time. The effort has been done in advance, and now it is very easy. Just pour it in without any fine-tuning."

"As for business training, it starts from the moment the project team is established. Director Long just praised us for teaching our best, but in fact he only talked about one side of it." Zhou Zhi smiled and said: "What we teach everyone is computer principles. , operational skills, as well as simple development and operation and maintenance work, which can be mastered very quickly.”

"Everyone here is a business expert, and what you have taught us are business processes and business skills, which are the general methodology for the operation of the entire industrial and commercial bureau, and they operate efficiently, accurately, and completely. However, these are What we learn from you.”

"So we can't be considered teachers. This learning process itself is a kind of healthy and complementary exchange. I think everyone is still very well integrated in terms of early demand collection and mid-term system development."

"Since everyone is a business writer, now it is turned into a system for everyone to operate. As long as you are familiar with the operation skills and re-train on the business, isn't it just a matter of learning what you write? To use the old saying in Manzhou, you are reaching into the kimchi. If you don’t catch ginger in the jar, what could be simpler than this?”

There was another burst of laughter in the conference room. Mr. Zhou's words had not been heard from anyone for some years, but it was really appropriate to apply them here.

"So the main task now is to facilitate joint debugging and testing." After Zhou Zhi waited for everyone to laugh, he became serious again: "But don't think it's easy. As I just said, a man who travels a hundred miles can only walk half a mile. Half, life is all here.”

"As far as I know, there are many people in the project team who have opinions about me." Zhou Zhi said: "Everyone is very urgent and wants to put the system into production as soon as possible. They think that functional testing has been completed during the early development. , why do we still need to conduct business debugging after deployment? Why can't it be put into use immediately?"

"Then what I want to tell you is that you are too optimistic."

"There will be bugs in the development process of any system. There are many reasons for the formation of such program vulnerabilities. Except for a very small number of them, they are caused by program errors. Most of them are caused by a lack of imagination in application scenarios." "What was our purpose in the last round of testing? It was to test whether the system functions set in the requirement document could be realized. What was actually solved was the most basic capability of the system, that is, the question of 'whether the normal workflow can be completed.' "

"But think about it, in real work, can we ensure that every operator operates [-]% correctly without making mistakes?"

"Many system bugs are hidden in places like this. When you operate normally, they will never be exposed. They will only be exposed when you make an input error."

"I will give you a simple example to illustrate the harmfulness of such a BUG. However, it is best not to spread the word outside. We only need to know internally."

"Some time ago, an embarrassing incident happened at the bank where our company opened an account. A teller made a mistake during operation and entered the customer's ID number into the amount field."

"Because the customer originally only took out a small transaction of 100 yuan, there was no need for authorization review, and the transaction was entered into the system."

"It wasn't until the batch clearing was done at night that this transaction was cleared in the system, and all the branch's cash accounts, corporate transfer accounts, and inventory accounts were cleared all at once, and the system was completely down."

"Why is this happening? Because this demand withdrawal transaction is considered an astronomical amount by the system. All the cash inventory of the entire branch is used for payment, and the amount is not enough!"

"What's even more exaggerated is that this is an inter-bank business, which itself has to be liquidated through the People's Bank of China and other banks. Fortunately, the system was down due to the clearing of cash inventory, and no liquidation text was sent to the People's Bank of China. Otherwise, it may have caused a complete The provincial financial system couldn’t open the door the next day.”

"Is this problem serious? How terrible is it if a province's financial institutions are shut down, even for just one minute?"

"But if it falls into the system, is it easy to avoid it?" Zhou Zhi asked: "Now comrades are very familiar with the system. They only need to set an upper limit for prompts in the amount input field, or when entering data The system conducts a large-amount authorization review beforehand. Anyway, there are countless simple ways to avoid this problem."

"But why did the problem still arise? In fact, it's just three simple words - I didn't expect it."

"Everyone here is a business expert. Such mistakes seem ridiculous to everyone, but in reality, if you can't handle it, it will happen, or it may happen."

"Even if the probability of it happening is very small, and it won't happen once in ten or twenty years, it doesn't mean that the consequences won't be serious once it happens. The example I just gave illustrates the problem."

"So how to prevent similar things from happening in our system is the focus of this debugging test!"

(End of this chapter)