A few tips for programmers to remember

1. Think clearly, and then write the code

A novice who has just entered the industry, in order to show his ability, he can't wait to start writing code when he gets the demand. It's a big no-no!

In my opinion, only 20% of the time is actually writing code. If you don't want to be clear, the other 80% of the time is fixing bugs.

640?wx_fmt=jpeg&wxfrom=5&wx_lazy=1

2. If you don't communicate, you will be blown away

I don't like to talk and communicate, and it is easy to make mistakes in understanding requirements. Finally, I find that it is not required by the product.

A lot of functions are pushed back and forth without communication.

640?wx_fmt=jpeg&wxfrom=5&wx_lazy=1

3. No one reads the document, but it still needs to be written

Most of the time, the function of documents is not for communication, but for recording. Most of the requirements are still communicated verbally, but if you do not write documents for recording, it will be easy to argue later.

640?wx_fmt=jpeg

4. Be sure to write notes

If you don’t write comments, you are digging holes for yourself and others, because after a long time, you will not be able to understand your own code.

640?wx_fmt=jpeg

5. Don’t expect demand to stabilize

Product demand is constantly adjusted according to business needs. It is normal to change demand. Don't complain. The only constant in this world is change.

640?wx_fmt=jpeg

6. Business over technology

If the technology does not serve the company's business, it will be worthless. The company's profit is the last word. Therefore, it is not recommended for everyone to pursue new technologies, but to pay more attention to the application of mature technologies in commercial companies.

640?wx_fmt=jpeg

7. Don’t take chances

Where you vaguely feel that there will be a bug, there will definitely be a bug.

640?wx_fmt=jpeg

8. Test yourself several times

Don't throw it to the testers to test after writing, and ensure the quality of the things you pass through your own hands.

640?wx_fmt=jpeg

9. Solve problems on your own whenever possible

If you encounter a problem you don’t understand, try to solve it first (90% of problems such as Google, Stack Overflow, etc. can be solved), don’t take a picture and throw it at others for help. Your boss and colleagues are not here to wipe your butt, but they really If you screw up, ask for help ASAP.

640?wx_fmt=jpeg

10. Use new technology with caution

Don't pursue new technologies. New technologies are all beta versions. Before the great god has written a clear Chinese introductory document, he will use it at his own discretion, and most of it will be dead.

640?wx_fmt=jpeg

Guess you like

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