The working principle of the internship summary

      Yesterday, I adjusted the interface with a female colleague in the front end. Yesterday, I wrote a document for her, and the url in it was correct. Today I gave her a screenshot of my local call. I want to show her the result. We adjusted multiple inners in the back end. As a result, she added it in every place, and she didn't confirm it with me when she saw the difference. Second, as a regular worker, the front-end fixed path format was not clear, and she didn't tell me if it was changed. After making a mistake, it will definitely not be adjusted. I went to her, and she asked me to find the reason myself, but never to us. As a result, we searched for the reason for a long time, but we couldn’t find it at all. I intuitively told me that her request was wrong, and I planned to change the agreement. At this time, our back-end master looked at the log and found that her parameters were wrong. I asked her to go to the inner and adjust it again. She was very impatient. She said that she was busy with other things. Another day, she was really spoiled. I don't want to do it again. When I talked to her, it happened that I would ask for a leave of absence after completing the assignment, so I was too angry.

     In the three months since I came to this company for an internship, the colleagues in our department are all very good. All aspects and tests, any problems will be dealt with immediately, you will not tell you, and if there are problems, they will follow up and deal with them. There is no one like that Female colleague, the problem came from her, she didn't find the reason, and she didn't actively communicate with you, she thought it was your problem, which delayed us for so long. There are also some regular workers. When they see that you are an intern, they get impatient before you speak. They say that you can take a look at yourself or ask someone else to find her again. They are usually women, but some people will patiently tell you that you want her. What should I pay attention to? What problems and pits are there? For example, the female product manager of our group, a new tester, wrote a test case for the first time to tell everyone. In our group's test, if you ask what happened to this bug, she will tell you, even if she doesn't know, she will tell you who to ask. I think that as a programmer, you need to cooperate with others, and treat other people's problems as your own. If there is a problem that you are responsible for that affects other progress, you must deal with it immediately. It’s just delaying other people’s time. If you can deal with it in 10 minutes, you can solve it immediately, immediately, and now. If you can’t solve it, you can find a solution. If it takes a lot of time and has a higher priority, you can say when it can be solved, but If it's a 10-minute bug, it should be dealt with immediately. I've seen too many people who don't know what the problem others want you to solve, so they start to get impatient, or they promise to deal with it and delay it for a long time.

      Technical issues can be learned, but attitude is the most important thing as an employee. Assigned tasks to me before. If I have never come into contact with them, I will take a pen and a notebook to record them, because I can't remember them, write them down and ask all the questions clearly, go back and look at the code and requirements, and write them out by myself Solve or realize the plan, so the efficiency is often very high, and it also reduces the time to ask others. This is a good learning attitude. Learn to record, learn to think in time, and learn to be very clear before you start. When communicating with colleagues, when bugs are very troublesome, you can't be impatient. Even if you're annoyed, you can't have emotions, and don't bring your emotions to others. If you have any problems, you should locate them in time and solve them immediately. Confirm and improve the efficiency of problem solving. If it wasn't for this experience, I wouldn't be writing or summarizing it. We are always seeing the gap between people and people, and when we experience this gap, we will think about the problem itself, and connect a series of things to form own principles.


       

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=324722041&siteId=291194637