What is a good programmer?
1 The code you write can be understood by others.
2 Be curious.
3 High development efficiency.
4 Good English, and good at using the Internet to solve routine problems.
5 Pursue perfection.
6 to understand product design
How to do it
1 The code you write can be understood by others.
First of all, you can't be lazy, the most earthy way to write a bunch of comments.
A better way, give each class and method a good name, and let the code speak for itself.
Ask your friends where they look struggling.
2 High development efficiency.
Good at using open source tools.
Reuse previous development resources.
Can quickly expand the scope of work, so that other small partners in the team can intervene in advance.
3 Use the network to solve conventional problems. Recommend some excellent domestic and foreign websites.
http://www.csdn.net/
http://www.oschina.net/
https://github.com
http://sourceforge.net/
http://stackoverflow.com/
http://code.google .com/
It is very important to learn foreign languages well. Many excellent resources have not been translated into Chinese.
It is very important to have a ladder ready. The one I have been using http://honx.in/_U8W8hIIaAzvZt80U
4 can solve unknown problems through exploration.
With the accumulation of experience, you will have a certain degree of operating system and programming language, which will help you solve some unknown problems.
Follow the vine to find the reason.
Make some reliable speculations and verify them.
5 Pursue perfection
Only in this way will you have the motivation to repeatedly optimize performance and user experience.
6 to understand product design
If you know the design, you can tell whether the product requirements have been deliberated and whether they are reasonable.
This is of extraordinary significance. Once you find that the direction is wrong and put it forward in advance, you can avoid detours and even repeated revisions.
Not taking a detour is a shortcut, a shortcut. It can increase the efficiency by a hundredfold.
If you find this article useful or have questions, please comment. Your feedback is my motivation to refine this topic.
The reason why it is called v1.0 is to continue to improve and nerves this topic, gather the experience of many people over to create a programmer's introductory guide, so that beginners can avoid detours.