The important thing is not the experience itself, but "studying hard", that is, to constantly challenge things beyond one's own ability - Jeff Atwood · "Programmer's Cultivation - From Good to Excellent"
This is a time when everything is moving at a high speed and the urban environment around us is changing almost every day. Even people who have lived in a city for a long time will inadvertently find that they have not been here for several months, and it seems that there are many roads that they do not know. This feeling of rapid change should be more pronounced in the IT field, where Moore's Law tells us that the computer performance that every dollar can buy will more than double every 18 months. This kind of knowledge replacement is more obvious in the field of application software development. A large number of frameworks and development tools have flooded into this industry, which has lowered the industry threshold and also promoted a large influx of labor. In order to keep up with the trend, developers have to choose promotion or change careers to maintain their competitive advantage. In fact, "The best thing a software developer does is learning. There is no necessary connection between years of experience and programming skills. After 6-12 months of working in any particular technical field, you're either proficient, or you've been there forever. Fuck off." Atwood's words pointed to the essence of an IT career.
One of the drawbacks of technological development is that people are becoming more and more lazy, and everyone wants to be a "hands-on party". If technicians have such a habit, it will bring about an increasingly low ability to solve problems. When a user accesses a link in the browser, from the moment the user enters the URL and presses Enter, until the response data is finally displayed on the browser, what kind of process is this? I'm afraid not many people can tell. How is the content entered by the user on the page converted into various data types by the framework? I'm not saying that you must learn network protocols and look at the source code (of course, understanding the underlying things can definitely improve your professionalism). But you at least need to know that the data submitted by the browser to the server is essentially a string of serialized Strings. The application server decodes it and sets it into an object named request, and then hands it to the application for type conversion and so on. operate……. For the increasingly complex system of the business, if you can understand the working principle of the software, it can help you to assess the approximate place where the problem may occur in advance, thus greatly reducing the time cost caused by line-by-line debugging. Moreover, even if you have the patience to debug line by line, you may not always be able to find the cause of the problem. Code is just one aspect of a program.
UNESCO put forward the "lifelong learning" initiative in the 1960s, but the development of the times seems to be just the opposite. The "hand out party" often does not like to learn. You can see that when developers search for information on the Internet, if they open an English page (or just a page with a little more English vocabulary), then they close it quickly. Such people obviously don't have a good attitude to study. First, they have a bad attitude when they are studying - they don't study English seriously, and then they have a bad attitude after work - why don't they learn the materials that are helpful to their work? In fact, many questions that cannot be answered on Chinese search engines can be found on some English websites. Open the English-Chinese dictionary and translate a few key words. You will find that English in the technical field is actually very easy to understand. . There is a saying in "Wei Xue": "To do it, the difficult will also be easy. If you don't do it, the easy will also be difficult." If you try something beyond your own scope, you may fail, but the possibility of success is also great. Yes. The origin of software technology is abroad, and you will benefit a lot from reading some translated works of Daniel. Some people think that the books written by foreign gurus can only be seen for fun. These readers should belong to the "hard-working code porter" or the like, or have seen too much the dark side of world affairs and gave up higher pursuits . Daniel expounds ideas and principles, and these things are many times better than those of books such as "XX Days of Technology".
There is also a group of people who never read "long" materials or read "thick" books. This is a sign of impetuousness and lack of understanding of learning methods. "Long" and "thick" articles and books, excluding those purely fictional ones, there are many systematic and comprehensive ones. Reading such a piece of information can solve a lot of technical doubts, and even give you a new idea to achieve the effect of inferring others. Knowing problem-solving skills is wonderful, but real achievement comes from solid accumulation. When reading a book, you must first read the catalog. If you have time, read its contents page by page. If you have no time, search and read according to the catalog. Some books look thick, but there is no very close connection between the front and back. It is also a way of learning to read a few chapters and read the whole book further.
Most of us are not "rich second generation", "official second generation" and "star second generation", we have neither a powerful "godfather" nor a brain as smart as Einstein. We have neither the pretty face of a star nor the luck of winning 5 million. But fortunately, most of us do not have serious physical and intellectual disabilities, and we do not have to work hard every day to get food. So, why not learn more?