Let's take an example of how to deal with things.

Let's take an example of how to deal with things.

In recent projects, it is not difficult to develop software into a language that supports 23 countries. The key is the multi-language coding problem, the language encoding in other countries is messy. It is too troublesome. Sometimes it is really unbearable. No problems were found during the processing. The software could be uploaded to Western Europe and East Asia ...... When the world is different (it is really a hell), there will be a problem. Every time the customers there report a lot of UI bugs coming to the Chinese mainland, they have switched their regional languages, but there is something wrong with them. I don't know if it's our problem or the customer's problem? It wasn't long before I joined the project team. I was working on another project. Now I transfer it to you. I am responsible for a module in a large project. I am really worried about how to solve the problem in multiple languages. From the perspective of the module architecture, I can only describe it in one word: Chaos. Especially when dealing with the problem of multi-language encoding, the most messy problem is that you cannot find the problem? If a problem occurs, it may take nearly one day to locate the problem. Here, I will first talk about the software architecture.

It can be said that the software architecture has been clearly understood by three layers in general. However, I personally think that the development team was still considering complexity, but now there are problems there, the software coupling is too high, which leads to a much larger job after I take over. But it does not matter. I can afford it. What I cannot understand is: I asked Code Sometimes I get vague answers. I don't know if it's my fault or what's going on? I don't understand it here. I believe everyone has encountered this kind of thing. When you have a problem, if you are familiar with it, what do you think? I think everyone has their own idea, right? What should I do? Start by yourself and enter the code world! It's okay to see it. It is basically stable, but when I run the system, there are more than one hundred warnings. We all know what the emergence of warning means in the software crisis. The most serious one is insecurity. Sometimes, the system is caused by a small warning, resulting in data transmission errors, resulting in a complete system crash, too many new, but there is no corresponding Delete. what's even more fascinating is that the char type is assigned to cstring for miraculous compilation. Strictly speaking, this is not allowed. It is also very insecure, and it is also one of the most garbled bugs produced in different encoding methods. However, the entire project does not seem to have a uniform type for processing strings. This may be caused by the individual habits developed by different people. I have not learned about this in detail. But one of them is my responsibility. I have to deal with these problems. Because these problems are not handled, the software will encounter the same problems in the future. I have been wondering why different garbled interfaces appear in different regions? In fact, I have read the code for a long time before I can understand it. The simple problem is that char is assigned to cstring. in different regions, problems will certainly occur, this is the so-called bug reported by the customer in the hell. It's too much, too much to change. I thought about it slowly, but it was not that complicated. I just needed to convert all the displayed items into Unicode. From a macro perspective, it is to make the display correct. As for how to handle it inside the system, I will not care about it for the time being! When the processing is complete, someone will always doubt whether the processing is correct. I formally took part in my work. To be accurate, I barely got a year. First of all, I accept criticism from others. But at the same time, my work thought is: to deal with the same thing, if you have handled the problem, someone else can tell you something wrong, but be sure to understand the cause. Don't be honest, and you have no feasible suggestions. To be honest, I encountered this kind of problem most feared in my work. When the process is correct, there is no problem, but others say there is a problem, but there is no way to tell where the problem is? I personally think, it can be said: This is not reasonable! I am very jealous of this. I just mentioned that I just graduated from college for just one year, but I have done a lot of projects, both large and small. It is a little less practical to get into the society. In the eyes of people who have experience in year 34, I am a little younger. There are too many things to learn, but it does not mean that I have no confidence. My pursuit of technology is no less than a person who has been working for several years. In any case, I have a positive attitude towards the opinions and help given to me by others. I sum up the following: 1. Do not always think that your approach is correct, others must be wrong. 2. Do not always admit that others are right and you are wrong. 3. There is no right or wrong in dealing with one thing, I just thought differently about the advantages and disadvantages of the problem. 4. When you work in a company, do not always think that you can get promoted, do what you need, and learn more, stick it to your own head. 5. Don't always think about new things, but don't go to challenges if you don't. 6. Don't keep escaping from work, we should take the initiative to undertake the workload, young people. I personally think, don't be afraid of fatigue. If you are afraid of fatigue, go home and hold your children. 7. Don't always complain about your life, or be afraid to work overtime every day, overtime is a good thing (of course, if you do not like your work, don't say that you have worked overtime, it's time to go to work, and it's estimated that your work will also be cool, I personally think that working overtime can both learn and do what I like to do, creating good conditions for future development and displaying value in the company (Unfortunately, my company does not allow overtime at all. If I want to work overtime, I have to write an application. If the leaders approve the application, I can only work overtime, but the possibility of approval is basically 0.1%.) I leave work at five o'clock every day, I usually leave the company at every day and take a bus home. According to the company's staff, I often volunteer to work overtime after work in the afternoon and the leaders may have opinions. So I am worried about whether my boss copied me because I went back very late every day! Fear me ~~! 8. If you learn more, you will not be afraid to starve to death. When you get there, you will have bargaining chips with others. Where is your value? It's in your brain! 9. If the company has some limitations on its own development, it is recommended to jump quickly, because the company can afford to consume, I can not afford, the truth is very simple, the company can develop in one hundred years, but it is impossible for it to have its own business in one hundred years. The company is still developing without me. It will also recruit a group of technical talents and cannot find its own development company. When I was young, my own values were not reflected and I could not make full use of what I learned, it is a sad thing. Finding your real value is the main thing !!!

the above points are also my profound experiences, but they are very suitable for me. As to whether they are consistent with other people, they are all people. Come on! Because we are all lucky. Let's look back and look up. We are walking in the technology preface. At the forefront of human wisdom. This is lucky! I sincerely wish that every friend who struggles in a technical position can fly with wings and make great strides ......

------ By beyondboy