This time, continue to read the progress of the last time, and record the points with deeper insights as follows.
Programmer is a behind-the-scenes worker
In the book, Jueying writes software for hospitals, and doctors (users) only evaluate whether the software is easy to use or not, but do not evaluate whether the programmers who wrote the software are excellent or not. This doesn't seem fair to the programmers, the code I've worked so hard to write doesn't deserve my evaluation. But this is a fact. What a software opens to users is its function and its interface. The user doesn't care how complicated the code behind a certain function is, he just starts from his experience of using the software. So, again, user experience comes first.
Are high scores and technology contradictory?
When Mr. Zhou reviewed the resume, such a resume was directly rejected because it was written that the scores of several courses were 90+, and then Mr. Zhou's logic was "he spends all his time studying and has no time to go. A real hands- on experience ". I don't think it makes sense to kill someone just because of their good grades. However, this tells us that your resume should be targeted. The other party does not care how many points you can get on the test, but only cares about whether you have rich technical reserves and whether you have corresponding project experience. In other words, it is to show what the other party wants to know. Those who are excellent in other aspects can be put on it, but they cannot be used as the main body.
Miscellaneous perceptions
One thing I feel is that, like Jueying and BOSS Liu, it took five or six hours or even overnight to adjust the bug. When I mentioned it later, I always didn't want to say the time I actually spent. On the one hand, it's "playing a swollen face and making a fat man." On the other hand, as far as I am concerned, it is indeed a waste of time to adjust bugs or write code. If I could think clearly at the time, it was really only twenty or thirty minutes. Or something over an hour. I think it's still a matter of experience. The more code you write, the less time you have to spend.
In addition, the director mentioned this kind of request to Jueying. There are a lot of requests, and it is not completed at one time. This phenomenon is still very common in actual software projects. But there is no way, the user is the first, although there may be countless words in my heart, what should be done is still to be done. But on the other hand, when writing code, it is necessary to consider the convenience of modification, which can be multiple functions, or use some prepared statements and the like. Unless you are refactoring code, try to minimize the amount of modification work. This is also a manifestation of good code.
There is also a little bit of insight, that is, don't say too much in advance, and don't brag too much. This is reflected in the fact that BOSS Liu recommended Jueying to the new company. When we are working on soft engineering projects, we always tend to think how well the functions to be implemented are conceived in advance, but in fact the final result is always quite different from the original idea. I think it is better to be practical at first. Of course, this actual estimate is also based on experience.
Then there is a little software industry, new people will always emerge one after another, the old people can only be eliminated by keeping the technology not backward, constantly competing with new people, and constantly learning. For our students, we will be newcomers in the future. As newcomers, we must continue to work hard. Time outside of work can be used to learn new skills, and newcomers do not have so many worries. This is also our advantage.