From the video of "Left God", I simply made a note.
1. (Requirements of work and company) A
few years ago, five or six years ago, or earlier, when you entered an Internet company or IT company, you did not need strong data structure and algorithm capabilities. Going in is writing and doing business. On the one hand, the number of users is relatively small, the workload is relatively simple, and the amount of data is not too large. As long as the work is finished, it is available, and more attention is paid to the functional things of the business. After applying for a few years, I can write a framework, simply build a database, and simply write some task flows. The database will use transactions. You can do things that imitate SpringMVC, which is enough to get the job done. But today I found that it is not working. I go to a big company or a better company for an interview. I often encounter problems with algorithms and data structures, and the proportion is rising.
Reason: The
early Coder was very concerned about the capabilities of algorithms and data structures, such as the Apollo on the moon, how much memory does the Apollo ship on the entire belt, not more than 1M-1024KB-1024*1024 Byte, KB-level memory, It will be able to land on the moon. At that time, those old-school Coders squeezed limited resources to the extreme with their strong S&&A capabilities, and gave full play to the mathematical and S&A design sense, allowing very tight resources to complete difficult tasks. At the beginning of computer technology, when the system started, system programmers wrote the system, and the system ran on the hardware. Only when the system is set up, users can complete the use-level work on this system. If the cost of this system is very large, a The logic is not well written, you have to eat a lot of resources, and your running time is relatively long. As a result, you leave the user with less memory. The hardware level of the computer was not so good that year, unlike today’s memory dynamics. More than 30 GB, more than 60 GB, the system was very tight at that time.
In the early days, the American Coder only tested the S&&A, system. In the face-to-face experience, you can collect some questions about the language, collect some questions about the system, ask the Internet, ask the database, S&&A is not good, you have to understand, know how to use it, and you have to go through a lot of practice before you can get through it. You can only think of a new problem, oh, the S&&A thing I learned before can solve it, and you have to write the code on the spot.
The data structure of the algorithm is difficult to practice, and it is not possible to practice for a long time. #贵的 is the most economical-Google.
Write the code as soon as possible. This kind of Code will gradually become lonely, because each company gradually divides its own fields, and enters the business field that they have grabbed. You must work carefully in this field, iterate carefully, and optimize Code, improve function, so S&&A inspection is also a kind of demand from the company.
2. (Examinee requirements)
①S&&A can be considered as a proof of absolute code ability and patience.
②It can be used as a proof of a good mind. The company likes a genius by analogy.
In the past, you could be an architect if you knew SpringMVC, but now you can’t, and the times have changed.
S&&A can't just rely on back and remember, the actual business requires smart and capable people to prove it.
3. (Difficulties in the learning process)
Introduction to Algorithms···
Learn Data structure &&Algorithm from "Left God"...