Starting from July 7th, by September 3rd, a Japanese .NET project, two months of development practice, learned some fresh things, written, and left after the reference.
1. Little experience in the project development process
1: Preparation of the project
Since July 7th, it is basically the real entry state of July 20, July 7th to 9th, is a partner above Japan to explain the project's approximate process and development statute, which feels Japanese This normative requirement is much higher than that of our domestic projects, because in the first half of the school participated in a domestic project developed by the college (only for a few days, come to the company), although we did in design more than Japan A lot, whether it is a database or security, but our development regulations do not have them, it is also what we have to learn to Japan (I have a good feeling for Japan is very careful), design them. It is also a dead, basic processing logic and page requirements are already done, we only need to implement the logical functionality according to their design requirements, this favorable aspect, that is, the overall development comparative specification, The final effect is also very good, but this also brought trouble to the detailed design. In this project, it feels the deepest, because the designers there are not very well understood, so some design is still in accordance with old design ideas. In some places, the superiority of ASP.NET is constrained. Here I want to say is that although it is not limited to implementation technology, if it is very clear about realization, the designed thing is still the final Efficiency will have a good effect. Another aspect is that this object-oriented development will definitely involve many public classes, public controls (defined as "common functions" "common functions" in Japan), this project is from Shanghai, Hangzhou, Dalian three places to develop, so in order to ensure the consistency of the project, these common things must be defined in advance, which brings a problem. "Think of things must be correct, and we must comply with our requirements. ", But facts are often not what we imagine. In the process of actually doing, there are many time to waste, and there is a feature of the Japanese project. I will not give you something needed. Wasted a lot of time in this process to write some things we demand, but suddenly one day has a common thing, realize the part of the features achieved by your code, you have to change your code, adapt to the whole The requirements of the project specification, there are more than two weeks in the development of the development, and the project team is in this state, so I think if I can determine these things when I start, maybe the entire project can do it. More than some (huh, just ideas, the actual general will always have such problems, this process, also exercise the ability to solve the problem, so I have to prepare for depression).
After these things, the project manager began to do Schedule, about Schedule, I think this actual role is that you must die, you must finish the fixed point of day, this project Feeling is more profound, because most of the members of the project team is a newcomer, everyone is working hard, but sometimes the technical problem is indeed painful, when the project is coming, I really understand the Schedule. The role, "I understand what to do, do a reference", because there is no practical to do, it is difficult to really grasp the difficulties of what you want to do, and the technical issues that may encounter, although there is no thing that can't be realized. But this solution is indeed a little headache. You don't know when you can come up with a solution. If you think about the time specified in Schedule, then I think this pressure is really unable, so I don't want to use it. Completely thinking about that schedule in your mind, it may be more than two days or three days, but next time you have a similar problem, you can solve it in an hour. At that time that exceeds Schedule, you can make it back next time, and eventually can be done on schedule. In the process of developing Schedule, I think this also requires a project's manager to achieve the entire project process, project group member, and the attitude towards partners. When a project is the first time, this may be a Ideal, I think our project team has experienced this development training. In the next cooperation, we must have better results. After all, we still cooperate, and it is the first time to contact the actual project. After this mill, I think the cooperation and communication will be better. 2: Development
After the preliminary preparation, the process is also a real experience of "pain and happiness" life. When there is a technical problem, it is also a problem, and it is also a problem. At the time of the carnival, it is like every day from hell to heaven, a circular tour from heaven to hell, a love, perhaps only our ordinary programmers can experience. During this process, truly learned, not just a technology, I feel the deepest is a kind of attitude and mentality to solve the problem, a good job habit, these are treasures that are infinite, because knowledge is always learning If you are not finished, the key issue is how to learn them, and use these things to practice, solve practical problems, and have encountered a lot of problems throughout the development process, whether it is technical or language communication. The business is not understood, leading to the error of the program logic itself; the technology does not understand, causing a lot of implementation, I don't know how to start, these have once again let my heart. After all, the company and school have a lot of different, the school can give up, the company can't, must do it well, this is a responsibility problem, this will be coming for nearly two months, it is indeed "responsibility" two The amount of the word, it is also a kind of man's attitude, the first in the society, I think there are many things that we want us to observe, think about it, try to do it, this is my original intention, So do more doing it. In the development, experience the most, the most experience is to read those such as the Tianshi-like Japanese design book, and watching the brain a mess, in the development of the two months, there are some programming experience, and Some "experience" that can't be said, when getting a new design book, the first thing to do is quietly understanding, a lot of detours in this project, a large part of this reason, too Urgent, often start coding when there is no clear understanding of demand, after writing a lot of code, I understand that it is fundamentally wrong, this process is actually a lot of time in white, if you can start painting A good understanding of demand for a while, it may not blindly appear in realization, but can shorten the development time. Another experience is how to face when encountering problems, when you start doing, you will encounter a lot of technical problems, how to think about these smart problems? The two months of experience is that first, think about the program code you have done before, is there a similar problem, when it is solved, there is similar to this problem, different It may not be able to immediately understand the correct solution, but can be inspired with a little bit, just this time about the JavaScript code used in the modification, it is inherently, but it is only a different manifestation in different places. Method. Furthermore, look at the colleagues have done a similar function. This is a little code to reuse. Maybe it's a few days of implementation, others have already been achieved before, especially in project development. Important, after all, there is a time requirement, unlike the school as purely learning to learn, the project is required to complete the customer's requirements on time, this is the goal.
If these two means have been used, they still have not found a solution, so they should use the "Help" file and online resources. This is an important way to learn new knowledge. I will not use it in my knowledge. It is necessary to accomplish a task with many people's power, and the network can provide this condition, so it is also a great advantage that it can use support, especially when the project has developed extreme difficult problems. Now I feel that the book is based on the system, but he faces the most widely learner, so there will be too many questions on a certain issue, but the places we encounter are often these special places (do it. After two weeks, if you have a problem, if you become a technical problem, you should go to reflect), so for books, as an entry, the problem is still a large part of the network. If this still can't find a needed answer, then I have to take out the killer: ask this master. The reason why this is in the end is because everyone has some of their own responsibilities. The master also has its own task. If you don't have to have already, don't go trouble, when you ask them, I really should really go to the province. I really can't find a way? If so, then in question, you must think about this problem in the process of asking them, why they can think of trying to solve this, and I can't think of it, it is an empirical problem, or the technical is not mastered. When you encounter a problem next time, you may wish to consider the problem to solve it in accordance with their ideas. If these steps still can't solve these problems, then there is only one possibility, the problem, I can't see you, I want you to take you, huh, but this is not a lot, it is true. Glock, you can communicate well on the designer, take out the solution we can solve. In short, there is no problem that you can't solve, only the problem of temporary no thinking. Step by step, a solution will always be found. Another important aspect, test, now I think I have the most lack of testing, may be related to the level of care, always ignore some small places, although the test steps are known, but there is often not followed by the correct process, possibly This is caused by the impetuous psychology of the real project, and pays attention to the test of this ring in the future project, not necessarily the steps on the book, forming its own set of effective test methods (May mainly be a method for its own weaknesses). In summary, there must be no impetuous psychology during the development process, and the task is completed according to the class. This is also a process of cultivating habits. No matter which aspect of work, a good habit will always bring good results. Another problem is also said that SCHEDULE, during the development process, for a while, due to variety of reasons, it is basically separated from Schedule's control, and it is estimated that the problem encountered is insufficient, and its own technical level needs to improve, design problems, In the common problem, the total of Lin Lin, in short, it can be fully developed according to Schedule, it is really "moon myth", in summary, can not affect the completion of the entire project, I can't solve the problem, I can put it a little, maybe Suddenly inherently in the next process, the problem will be solved. So don't hang on a tree.
