1. develop my practice
(1) carefully research prototype, especially responsible for their own part;
(2) for part of their responsibility, each business function to draw a flow chart;
(3) After a good draw business process diagrams, study project structure, each layer is mainly what to do and what is the association between each layer
(4) after doing the above three steps, I am passionate start writing code before writing the code I will look at the seniors how to write, try consistent coding style, and then put their own thinking logic written comments, and then follow the comments while thinking, while writing;
(5) due to lack of experience, their technology is not mature and tight schedule of the problem, in order to be consistent with the overall R & D team style in the process of writing code, met some of the ways he had never seen before, at this time, in order not to drag the progress of the team, I chose to check roughly how to use these methods, detailed studies will not be used directly;
(6 ) in the development process, I am used to all finished, and then one by one test;
(7) does not solve the real problems encountered I will promptly ask the older generation;
(8) regardless of Products, as well as front-end R & D and R & D predecessors tell me what I always confident because of their lack of experience is not enough to completely listen to everyone.
2. Lessons Development
(1) later developed, from the fourth step I started to make mistakes, not to do wrong, but when looking at the older code, completely lost their judgment, consistent style, does not mean that the code to exactly the same wording, I want to grow, or to have their own ingredients, can learn from the experience of their predecessors, but not copy desirable;
(2)In the next fifth step, I made a mistake, and that is a method unfamiliar in the absence of careful study on the direct use, do not drag the progress of the idea is good, but the blind though they may use their own development speed speed up, but too late in the test, they might cause a lot of trouble, so in the end still have to figure out how to use, do not blindly;
(3) the sixth step, I can not escape the mistakes, this approach is not too wrong, but personally after participating in project development, I feel this way is quite suitable chiefs, for the development of white, or select a block to write a module measuring a safer, to ensure that all have to write their own code quality can be used, as long as a module pass, pass behind it, if you select all finished retesting, bad luck, then, to write all possible problems in your code, and put all the problems piled together, time is tight situation, to solve tricky. Therefore, personal recommendations, if white or research and development, it is best to write a test piece until experienced, cut into big brother, and then select all finished and then measured way;
(4) the seventh step, I was not guilty of wrong, but because of their not careful enough problems, many problems can be resolved obviously careful, but then he always ignored the details, this offense, must be fiercely punch to their brain, long lesson;
(5) if it is write your own code does not achieve the desired results, but it is no cause personal recommendations ask the older generation, it is best to tell seniors how to do their own, what kind of effect you want to achieve now is what effect, rather than go directly to allow the seniors to look at your code, look at the code takes time, seniors generally have a lot of things to be busy, directly to let them look at the code may be wasting their time if seniors to find out directly from your business logic in your question , you can avoid wasting time too long predecessors;
(6) Although the lack of experience, can not completely deny yourself if there is a direct challenge to communicate With a question rather than fully obey all the words;
(7) I do not believe they can not be too much, can not be too believe in themselves. The former is for Article lessons, which means that the code is not written as expected, please check your business logic is correct No, Do not trust their own thinking logic must be right;
(8) Do not be afraid experiencing problems Do not worry, be brave to solve, a problem is normal, we must find where the problem in a hurry will only blind guess where the problem lies, so only half done, maybe even half are not, so in case Please be sure to stabilize the problem, calm analysis to identify and resolve the problem.
3. mentality
from the start of passion, to their denial and disappointment at the end, but just one weeks time. Fortunately own thick skinned enough, quickly adjusted the mentality regain confidence and combat effectiveness. Although first developed themselves very far away from the expected results, is a failure, but we can not give up, give up on themselves, but to their own good summary of where the development of this issue, continue to learn and gain experience, only with great effort, will make yourself effortlessly!
Now, I'm fighting is a bursting of me, though poor technique, but as long as the ongoing efforts, I believe that will not leave the tears did not technology, but also will not let this process and help encourage their disappointing.
White can hope to develop their early experience, no tears, no technology.
Finally, we emphasize that people must be brave to ask questions, do not ask do not think the problem is simple. With our group of small brother then encourage people to ask questions: everyone came to be so, this will not be finished tube asked how people say you have to remember, and the height of your predecessors is not the same, even if others will say you are normal, that is not will not, as long as the future will be asked, which is harvested and growth. Ask questions, it will grow faster. Of course, generally they are good, we are very happy to solve the problem, such as bigwigs people in our group are good.
Here again I wish, can, like me, work has just started, will be able to experience these great predecessors.