First project summary, Project Summary

First project summary, Project Summary

I had a hard time in my previous internships. I felt that I had never done the right thing. I had a big job after my graduation and mainly participated in the development of the product PC. This experience made me more clear about the responsibilities of the front-end job, front-end engineers cut the graph is basic, js is necessary, and engineer three words are the most important. The qualified front-end should be handled only by giving me a backend interface and the rest. I am forced to say that it is necessary to take a close look. Of course, the cooperation and negotiation with the background are also very heavy. There is a lot of technical communication between the front and back ends. For some slightly rough data front ends, the backend can be better processed. At this point, when we need to cooperate with the negotiation, who will do it? Who is more convenient? Will this happen in the future?

Although I have taken charge of some tasks, the core technical problems are solved by the help of the boss. Looking at the code written by the boss is so advanced and elegant, the gap is huge. At present, the first version of development has been launched. I can only say that I have gained a lot of experience from it. As for the major technical improvements, I am not sure what to say. After all, I have not understood some technologies, you still need to review it and think about it.

Summary:

1. flexible use of tags, focusing on semantics, turning over large websites in the future to see how their webpage skeleton is arranged.

2.css should continue to cultivate. In many cases, it is necessary to "open" from the inside out to reduce unnecessary restrictions and widths. Take a closer look at the basic principles to learn more about them, such as vertical-align and line-height.

3. browser compatibility. The current situation is that it is not necessary to be compatible with IE6, 7. However, incompatibility means to ensure that there will be no major confusion in the browser of the lower version. Compatibility with the lower version is currently a serious problem for me and requires more accumulation.

4. The schedule should be reasonable. You should first think about it and then do it. If you cannot come up, coding. Development should be done in one breath, and don't have the idea of leaving a hole before entering it. The ghost knows if I can remember it in the future.

5. Be familiar with fiis, git, and mac terminals. What kind of firewood should I cut when I am not familiar with knives?

6. It may not take long for me to look back at the project summary and I think the current technology level is too low. Well, I look forward to breaking through the cainiao stage as soon as possible.