1. Think clearly before writing code

Newcomers to the industry, in order to show off their abilities, can't wait to start writing code as soon as they receive the requirements. That's a big taboo! In my view, the real time spent writing code is only 20%. If you don't think it through clearly, the other 80% of the time will be spent fixing bugs.

2. If you don't communicate, you'll end up with a broken head and bleeding face

Not being talkative and communicative can easily lead to misunderstandings of the requirements. In the end, you finish building it only to find that it's not what the product required. Many features are pushed back and reworked because of a lack of communication.

3. No one reads documentation, but you still have to write it

The role of documentation is usually not for communication, but for record-keeping. Most requirements are still communicated verbally, but if you don't write documentation as a record, there will easily be disputes later.

4. Be sure to write comments

Not writing comments is digging a pit for yourself and others, because after a long time, you won't even understand your own code.

5. Don't expect the requirements to be stable

Product requirements are constantly adjusted according to business needs. Changing requirements is perfectly normal. Don't complain; the only constant in this world is change.

6. Business trumps technology

If technology doesn't serve the company's business, it is worthless. Making money is the absolute principle for a company. Therefore, I don't recommend that everyone chase new technologies; instead, pay more attention to the application of mature technologies in business companies.

7. Don't trust to luck

The place where you vaguely feel a bug will occur is exactly where a bug will certainly occur.

8. Test it yourself a few times first

Don't just throw the code to testers as soon as you're done writing it. Anything that passes through your hands should be quality-assured.

9. Solve problems on your own as much as possible

When you encounter a problem you don't understand, first try your best to solve it (90% of problems can be solved with Google, Stack Overflow, etc.). Don't just take a screenshot and throw it to someone for help at every turn. Your boss and colleagues are not there to clean up after you. But if you've really messed things up, ask for help as soon as possible.

10. Use new technologies with caution

Don't go after new technologies. New technologies are all beta versions. If you take it upon yourself to use them before the gurus have even written clear Chinese introductory documentation, you are mostly asking for trouble.

Original URL: http://www.techug.com/post/funny-programmer-pictures-2.html