1. Think before you code
Novice, in order to show their ability to get demand can’t wait to start handwritten code, taboo!
2. If you don’t communicate, your head will break and bleed
He did not like to talk and communicate with others. He misunderstood the requirements and found that he had to work overtime and rework.
3. No one reads your document, but you write it anyway
Most of the time, the role of the document is not used for communication, is used to make records, most of the requirements or through oral communication, but do not write documents to make records, the subsequent easy to quarrel.
4. Be sure to annotate
Over time, you can’t even read your own code.
5. Don’t count on steady demand
Product requirements are constantly adjusted according to business requirements. It’s perfectly normal to change requirements. Don’t complain.
6. Business over technology
Technology is worthless if it does not serve the business of the company. The only reason is for the company to make money.
7. Don’t take any chances
Where you can vaguely sense a bug, there will be a bug.
8. Test yourself a few times
Don’t write it and throw it out to the testers to test what you’ve got in your hands. Make sure it’s good.
9. Solve problems on your own if possible
When you encounter problems you don’t understand, try your best to solve them first. Don’t always cut a picture and throw it at others for help. Your boss and colleagues are not here to wipe your ass, but if you really mess up, ask for help as soon as possible.
10. Use new technology sparingly
New technology is a good thing, but it is not 100% sure. If you use it on your own, you will probably die.
