Looking back now, it's all unbearable. I think back then when I was a fool and didn’t ask for answers when I encountered a problem . In the end, I didn’t understand anything except that the problem was solved. My experience now tells me that if there is enough time, it’s best to find the cause of the problem. I have always believed that the process of identifying and solving problems is the greatest help to myself. But when there is a real problem, sometimes it is extremely tangled and annoyed, but the problem still needs to be solved, it is impossible to bypass this problem, once this problem is solved by others, I will lose another opportunity to grow. And the impression in the hearts of others is one point worse. Therefore, when you encounter a problem, calm down and think about it more, and if you want to understand the problem, the answer may come out.
Now summarize some problems in the development. The first point is the problem of interface calling. All modules in the system pay attention to high cohesion and low coupling, so that the impact of module modification will be smaller, but in many cases, low coupling cannot be achieved, and the degree of coupling is very high. High, if the modification of the module is small, it is fine. If the modification is too large, the impact will be very large, so specifically, it depends on the specific situation, and consider whether the interface may be adjusted. This must be considered. Clearly, try not to couple other people's things, but if it is the same module, in the case of implementing functions, the changes should be as small as possible. It is not that the more code the better, the key is to look at the code quality and construction period.
The second point, in terms of front-end selectors, use the id selector with caution. Many times you think that this element may be unique, but maybe an id with the same name may appear at any time . If you have to use an id , add an id in front of it. Restrict the domain, such as formid and the like. Some time ago, the problem in this area was changed, and many changes were made. In the past, many components were one-to-one, so using id was no problem, but later changed to many-to-one, Then it is a tragedy, all the components "involved" need to be modified.
The third point, in terms of learning, many people may not be satisfied with such a little technology in their work, and they may study some technologies during business time. This should be a very good aspect, but sometimes you feel that the technology is stagnant, and you are very Hope to break through the bottleneck, but there are many restrictions. Do you have a very deep understanding of the tools used in your work and the platforms developed? No, in fact, the platforms we usually complain about are integrated with the efforts of many generations of programmers. Although many of them are not commented, it is very interesting to take a look. It is very easy to understand, then, think about whether there is any alternative method for implementation, and the method with better effect, then don't move, just think about it, and then write it down, when, in a technical meeting On, say it all, this might work really well, and then the techniques you learned in your spare time might come in handy. Researching and understanding the platform also has a very big advantage. Our daily work is basically inseparable from this platform. Once you fully understand this platform, the next work is not like a duck to water, maybe the next step is to get rid of the specific development work. . Generally, whoever is coding there is someone who doesn't know much. Those who know are watching the coding of those who don't understand. Anyway, that's what I think.
Fourth point, in terms of office life, do not discuss others in private, because the person who is talking with you about whether or not others may usually like to talk about others. Today you are talking about others with him, and tomorrow may be the person he is talking about with you. Talking about you and betraying you, alas, lessons of blood and tears.
The writing is rather messy, so let's do it first, and then look back at it later.