project level
Solve technical problems independently
In daily work, you should ask more questions to clarify business problems to avoid rework; but when you encounter technical problems, don't always rely on others and try to solve them independently . In the long run, you will form your own methodology for solving problems, and your ability level will also increase accordingly. promote.
Think more about why
In daily life, don’t just follow the CV method and complete CRUD; instead, think more about why you use it this way and learn the reasons for using it this way . For example, why adopt the MVC pattern? Why use the Controller/Service/Dao layered model? Why use Redis? Instead of local cache or MySQL?
Do more challenging work
If you just do some CRUD on single table or multiple tables or tinker with some simple functions, in the long run, it will be difficult to grow quickly, and you may just change from a young CRUD-Boy to an older CRUD- Boy. The work content should be from point to line, point to surface, and the challenges should gradually increase . The focus ranges from a part of the function, to the entire function, to the entire module, or even the entire system. Don't just satisfy yourself, gradually do more challenging work.
Learn quality projects and code
To put it simply, when you see something good, think about it, and when you see something bad, you should reflect on yourself. Choose a good project and learn the project's architecture, selection, and three-high strategies from the top level; learn other people's excellent code and learn technical practices from the detail level .
Summary and focus on the implementation of general solutions (important)
Although different projects have different businesses, the technical layer still has some common solutions, such as unified interface parameter verification, idempotence, interface current limiting, asynchronous execution, custom annotations, interface optimization, distributed locks, logging, etc. Pay attention to the implementation of the general scheme of the project, and then make extensive inquiries and summarize the excellent general scheme . You will be able to handle the same scenario again in the future.
Empower current projects with new technologies
When we learn some new technology, if we don’t practice it, we may quickly forget it. Therefore, after learning a new technology, think about the scenarios in the current project where this technology can be used, and try to use the new technology to practice, so as to kill two birds with one stone. Not only refactored and optimized old code, but also implemented new knowledge. Of course, when using technology, remember to fully test it and not affect the operation of existing functions.
Participate in project-related technical exchanges
During the project development process, there will often be various exchanges such as technology selection, technology sharing training, code review, various technical reviews, system tuning plan discussions, etc. Don’t turn a blind eye and actively participate . On the one hand, it can promote mutual learning and understanding. At the same time, when you have a project that you are interested in, you will have a greater chance to participate; on the other hand, it can improve your ability to argue and battle with the interviewer in the future.
learning level
Systematic and professional learning
When we learn knowledge in a certain field, we just copy and paste at work and learn in scattered ways. Although it can solve the problem temporarily, in the long run, it will only be a glimpse of the inside and a superficial taste, which is not conducive to ability improvement. Therefore, when starting to learn a certain field, it is best to study systematically and in-depth through official documents and high-quality professional books. This will comprehensively improve the understanding and application of this knowledge.
Studying requires taking notes and summarizing
A good memory is not as good as a messy writing. Whether it is reading technology or other books, if you just browse them casually, it will be difficult to leave a deep impression. You may forget it after reading it, so during the learning process, take notes on important content, outline the context of the content, and use your own digested understanding to make notes through summarizing articles, xmind mind maps, etc., to make it better. Master the content of the book.
Apply learned techniques to current projects
Applying practice is a good way to master a technology. When we learn a new technology, if we only learn the theory without practice, we may not have a deep understanding of the details, etc., which often leads to high ambitions and low ambitions, and talking on paper. Therefore, when learning a technology, think about whether it can be applied to the current project; if the current project has been used, think about its specific implementation and whether there are shortcomings and whether it can be optimized. In short, striking the skills you have learned while the iron is hot and practicing them in current projects is probably one of the best ways to master this technology.
Learn from high-quality technical articles (especially technical accounts from major manufacturers)
One bad thing about some technical books is that they often focus too much on theoretical knowledge without combining it with actual implementation scenarios. As a result, after many people learn it, they often don’t apply it well because they don’t understand it in conjunction with specific scenarios. Some high-quality blogs and WeChat public account articles (especially the technical public accounts of major manufacturers: Meituan, Alibaba, Tencent, etc.) often share some technical articles based on the problems encountered in actual production. Because these articles are close to actual production scenarios, you can better understand them after reading them. They are one of the best practices for applying theoretical knowledge in actual scenarios.
Learn from high-quality open source projects and source code
As the father of Linux said: Talk is cheap, show me your code. By reading the source code of high-quality open source projects, you can most directly understand the code design and implementation of open source developers, and pay attention to the code implementation methods of various design principles, design patterns, and design ideas. In the long run, you will be able to greatly improve your coding level.
Choose a specific technical direction to delve deeper into
There is no limit to the sea of learning, and knowledge is endless. As the market becomes more and more popular and people get older, the advantages of mediocre generalists become smaller and smaller. From an economic perspective, you should hone your comparative advantages. There are specialties in the technical field. Choose a technical direction that interests you and has promising (financial) prospects, and study it in depth to polish your technical advantages .