&http://www.aliyun.com/zixun/aggregation/37954.html >nbsp;
Do you still want to program when you are 50 years old? The topic is hacker news, but we can see that really successful programmers like John Carmack, Peter Norvig, Jeff Dean, Even if they are no longer young, but still passionate about programming, what are their differences and what is worth our learning?
1. Select a small subset of the current science and technology field, close to it, embrace it, and try to advance this small area of development.
2. Understand the pros and cons of different data structures and algorithms, not just in memory, but also in disk performance.
3. First of all, understand your field, and then put aside the computer, like ordinary users to observe and experience.
4. Always be ready (both in ability and in psychology) to explore deep, not just one or two, but several layers. You know, whether you can do it in a program, it's closely related to the depth of technology you can reach.
5. Use your imagination and always ask questions like "Is there a better way?" The best way to do this is to think outside the box.
6. Never quit prematurely, don't write the same piece of code two times, and don't name a variable as a subset of another variable. If you don't understand these rules, you might argue, but once you do, they can help you write better code, or you'll always stay at the level of a junior programmer.
7. Learn how to benchmark, learn the day you will find the world will be different.
8. Learn how to distinguish between trivia and detail and focus only on the details.
9. Don't always compromise with your users and managers, and sometimes you should let them know that what they think is not so important.
10. Write a frame, whether you plan to use it or not. This process will make you learn something that you can't learn in other ways.
11. Teach others what you learn, whether it be a mouth or a writings, you will find yourself reaping a lot from this process.
12. Find some other code written by others —— they achieve important functions, but they are not very clever. Rewrite them and then tell yourself foreverFar from the same mistakes.
13. Run your own business (service or product) at some point in your life. You can learn programming skills that you can't understand when you're an employee.