Work habits and experiences in software development

1. The mobile phone is always in use. I have suffered a loss. my mobile phone has no power or my mobile phone has stopped. I have waited for another phone number. It's really hard to say that! Moreover, I feel that no matter what you do, as long as you do not leave the community, your mobile phone is still in good use, whether it is a job or a family, the phone is essential!

2. be punctual and trustworthy when you do something: Once you agree to someone else, you have to be trustworthy. If you have an appointment, you have to be punctual. This is a basic principle of work, A loss of an appointment may lead to a great opportunity and even a bright future!

3. WriteProgramWrite more comments. That's right: When I first started writing a program, I didn't like to write comments. I thought it was too cumbersome. Now I don't think so. Without comments, I felt something was missing, if you want me to see it without commentsCodeIt is simply suffering. The program is written by you, but it is not used by you alone. It is a matter of professional ethics not only if you understand it clearly, but also if you want others to understand it clearly!

4. try to keep the style consistent: with the accumulation of writing program experience, you may write the same function code differently in different periods, so pay attention to it, if you want to write data, you need to save the same style, so that you can quickly pick up your ideas during future maintenance!

5. if you want to write complex code, you have to prepare a draft first. If you don't want to understand it, you should first make a demo, test it, and then, preferably consider efficiency, security, and so on, it's not just about implementing the function. If you try to make things round, it's okay!

6. if you have never touched on some features, you can find a solution on the Internet. Do not blindly trust others. It is best to read and understand them first to see if their code is missing. You can also use Baidu, google has a lot of code, and sometimes finds that the Code on the Internet can be used, but it is not the best, and we mainly learn some ideas. As for the detailed technical implementation, then you can combine your own reality!

7. it is best not to indulge in technical details. In the end, technology is only a means to accomplish things. What we need to think more about is how to accomplish these things efficiently. The process is very important, but sometimes the results are more important, just as many people prefer to write controls on their own and reject third-party things. I don't think it is necessary, as long as third-party things can achieve what we want, we may as well "take it here ".

8. if you have time to look at the code and software of other people, you may not have to fully learn from them. However, you must consider how to implement the software of other people from the perspective of "what is true, the presentation form and architecture design have been improved without knowing it.

9. Keep learning. Since I have done software, I personally think that learning is an essential habit. I don't have to follow suit. What new technologies do I have to learn? But I want to improve my skills every day!

10. the technical force must be concentrated. Today, more and more software development technologies are available, and our energy is limited. We cannot learn everything. We must have our own technical core and technical strengths, as for what technologies are good and what technologies are not good, there is no need, there is no absolute good technology, only good software!

11. Focus on accumulation, summary, and don't forget to write the code. You should accumulate the well-written and mature code, have your own database, and constantly improve your technical database.