Summary of the IDC Charging System

Source: Internet
Author: User

The charging system for the personal data center was completed yesterday. I am very happy to see it as a page of my history. In the process of making this system, we have all experienced the problem. Let's make a brief review of these experiences and leave them to future users to witness their own growth.

 

This is because the system should not only be integrated into the idea of hierarchy, but also the design mode. The design model was so superficial that it was used now. At that time, my mind was too big to be confused. Although the teacher gave us a lot of guidance, it is still quite difficult to implement it. At the master's suggestion, I plan to add the design mode first. So I went to learn the design model again, but I wanted to put the design model into practical use. It was actually yunyun.

 

At that time, my work was delayed. I told myself that I had to find a breakthrough. Otherwise, I would never go on. So the system started to imitate.

 

I also want to say a few more words about imitation. When I typed the three-tier example, it started with imitation. At the beginning, I used C # As An Example of Wang Jibin. What I understood was not very good and many things could not be understood. Then I imitated Jingyuan's login example, and felt that the example she wrote was closer to us and easier to understand. When I think about it for the first time, I can understand the idea of hierarchy, but there is still a distance between what I want to be myself. So I started to think about it for the second time. With the gradual deepening of understanding, I gradually had my own ideas, and it was easier to implement the second time. I know that imitation is, after all, an imitation. To truly convert it into my own things, you should add your own ideas on the basis of imitation to complete it independently. Finally, you have completed your own example independently. Layer-3 examples have been used for a total of four times, from ignorance to fuzzy understanding.

 

I think the data room charging system is also acceptable. At that time, the first line I imitated was the example of Liu's login. The design model it added was "appearance", "Abstract Factory + reflection ", in this way, I began to repeat her example several times from drawing a picture, followed by the second line and the third line, and gradually understood and had my own ideas, in this way, I started my tour of "charging system for personal data centers.

 

The real start time is 5/13-8/5 for nearly three months. This time is too long for anyone. During this period, data collection was delayed for more than half a month. Now it's incredible, but it actually happened to me. At that time, I always thought that how the teacher did not cooperate, so I could only find out that these are due to strong resistance and fear to new things. A lot of time has been wasted when you reflect it. This wastes a lot of valuable time.

 

The next step is about our graduation. There are a lot of inconveniences and a lot of time is wasted, and the system is dragging on.

After all things are handled almost, the system is actually started. When I was working on the system, I found that I didn't understand the basic syntax and usage. This reminds me of how I walked through the "student management system" and "Computer Room charging system. I remember that when we were working on two systems, we had to implement the system simply to implement the functions. Basically, we had to work on the basis of the source code, and a lot of code was hard to understand. Now, there is a dilemma: no source code, only functions, let us implement it ourselves. One of the deepest feelings is that the debt will be paid back sooner or later.

 

 

Small gains:

Since I understood the first line, I have been drawing and coding. It is difficult to constantly add new knowledge, but it is relatively steadfast. At least all the things in this system are self-implemented. I have learned a lot from the system:

1) Knowledge of the most basic programming languages: loops, arrays, functions (with parameters, without parameters), processes and their differences

2) Basic knowledge about databases: database connection, database commands (add, delete, modify, and query), and data adapters.

3) Try new knowledge: design mode, configuration file, sqlhelper, stored procedure + transaction, trigger + transaction, etc.

In short, there are a lot of GAINS.

 

Major problems:

As the system goes on, many problems are exposed, such as being not good at summing up, making excuses for delay, being less serious about learning, and resisting new things. These bad habits have always existed. This is what I need to learn in the future and must be improved.

1) I am not good at summing up. I have published it in Netease's blog -- <summary and reflection> and I will not repeat it here.

2) I would like to say a few more words about delay: We don't have time, but we forgive ourselves too much and hurt ourselves too much. My system was extended three times until the master told me that I was not allowed to postpone the course, and I had to wait for the system to take a short break in the morning and afternoon, I also spent another half an hour at noon. It took me 2 to 3 days. The biggest thing I felt at that time was that I could do the same thing! At that time, I didn't feel tired. Some were just excited and confident.

3) The learning attitude is not serious. We should not learn too mechanically and think more. The last time I followed the master and Zhang Bo for the ten-phase verification system, I found that the student system was completed and the function was also implemented. But you asked him how he got the data, he answered "I don't know", but I couldn't understand it at the time. This is the implementation idea. I can figure it out through a few buttons on the interface, and I don't need computer knowledge at all. I don't think the functions can be understood, but the logic is unclear. Then I asked a few questions and found that they had similar questions. I really want to tell them that the debt will be paid back sooner or later.

 

Summary:

Summary is very important!

Don't make excuses for delay. The parkinson's Principle "How long can it take to complete ."

Debt is always paid back.

Imitation is a learning method, but remember not to imitate mechanically. You must have your own ideas.

 

 

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.