http://blog.csdn.net/pipisorry/article/details/48896589
Recently sorted out some of the reading and the work of the programmer-related articles, put here and share with you, hope is preparing for work or work soon some confused programmers can take a look at the coffee. The work experience of a programmer
[Share 8 years development experience, talk about personal development experience, clear oneself development direction]
[How is programming in real work different from school?] ]
[10-point career advice for new entrants]
[Doing the right thing, waiting to be expelled]
[colleague skill is inferior to you, but the boss is to appreciate him, why. ] About programmers and code
[What are the excuses for programmers to write low quality code for themselves?] ]
[Do not die, do not die, measured by the amount of code to measure the performance of programmers (LZ said can be measured by the number of bugs!)]
[Why Google has to enforce strict code-writing specifications]
[8 ways to be a better programmer 8 Ways to become a Better coder]
[Programmer Technology Training Strategy]
[Why the future is the world of the whole stack of engineers.] ]
[How to become a good all-stack engineer]
[translation] How to become a good machine learning engineer
[How to become a data visualization engineer.] ]
[The only way to learn new things]
[What kind of work experience does an algorithmic engineer.] ]
[What are the classification of algorithmic engineers now?] ]
[How to write unmaintainable code good codes can find work, write not maintainable code, can not lose work]
from:http://blog.csdn.net/pipisorry/article/details/48896589
Ref