Hello everyone, I am Cang He. In the tide of technology, we often face a question: Is it worth learning those popular frameworks that are not used in work ?
As programmers, we all want to be on the cutting edge of technology, with the latest skills and tools. Learning new hot frameworks can energize us like a magic prop, allowing us to cast even more powerful procedural spells. Moreover, the new framework usually has a lot of cool features and conveniences, just like adding a trendy graffiti to your code, making your application "shine and shine " .
However, don't forget we still have work to do! Investing time and effort into learning a new framework can sometimes feel like digging one pit, only to end up in another. Just like when I learned sofa-boot back then, I spent a whole weekend learning the framework knowledge, but the boss assigned me a completely unrelated project the next day. Do you think I wasted my time for the new framework used in the new project? Therefore, before learning a new framework, we need to carefully weigh it to ensure that it is really beneficial to our work and will not let us fall into a pit.
I believe that most people are facing such problems. What I will share with you today is the problem of an aquarist in programming navigation and the suggestions I gave. I hope it can help you.
1. Problems
I would like to ask Mr. Canghe, is it necessary to learn all the popular frameworks that are not used in daily work? For example, Dubbo, Kafka, RocketMq, and K8s are popular in the market, but Springcloud, Alibaba, and RabbitMq used by the company seem to be useless When it comes to K8s, is it necessary to learn this kind of framework that is popular in the market but not used by the company? What should I do if I don’t use it until I forget it easily? Is it necessary to pack these unused frameworks on the resume? If you ask about deployment-related cluster production issues, is it easy to be exposed?
2. My answer
Hello classmates, in response to your question, the following are some of my personal suggestions:
For popular frameworks that have not been used in daily work, I think it is still necessary to learn !
First of all, learning these popular frameworks can broaden your technical vision and breadth of knowledge. An in-depth understanding of the working principles and usage methods of other frameworks will help you better understand the entire technical ecosystem and improve your comprehensive technical capabilities. In addition, mastering the advantages and disadvantages of different frameworks can provide you with more choices and opportunities for your future career development.
Secondly, the reason why the popular framework is popular is that many people and companies use it, and the framework can be popular in the market by virtue of its unique advantages. It will be helpful for you to learn.
During our interview, technical breadth is also an indicator of assessment.
However, if you don't have a chance to apply them for a long time after learning these frameworks, it is indeed possible to forget some details. To avoid this, you can try the following:
- Hands-on project: Do-it-yourself a small project, applying these frameworks for development and deployment. Through hands-on practice, you can solidify your knowledge and maintain familiarity with the framework.
- Participate in open source projects or personal projects: Actively participate in open source projects or personal projects, and choose projects suitable for using these frameworks to contribute. This can not only consolidate knowledge, but also exercise your actual development ability.
- Learning resources: Organize and save the notes in the learning process, including official documents, tutorials and your own practical experience. In this way, when these frameworks need to be used, they can be quickly reviewed and reviewed.
- Take notes and write a blog, and publish it to CSDN or Nuggets, Zhihu and other platforms
As for whether to display these learned frameworks on your resume, it depends on your personal situation and job search needs. If these frameworks are relevant to your expected job position, and you have a good understanding and mastery of them, you can list them on your resume. But remember, the content on the resume needs to be authentic and credible, and only listing the name of the framework without practical application experience may arouse the interviewer's doubts.
Make good use of words such as "master", "familiar", and "proficient". For frameworks or technologies that are not used in actual projects, generally write "familiar". proficient in the word.
During the interview, if you are asked questions about deployment-related cluster production, you can honestly answer that you have no actual production experience with certain frameworks, but you have learned systematically and applied them to your own projects, you can tell us For your own understanding, take Dubbo as an example, you can talk about the difference between it and SpringCloud, and compare the principles between the two. At this time, even if you have no actual production experience, you can explain the technical principles clearly, which is almost the same.
For cluster-related ones such as K8s, it is recommended to practice it several times by yourself and take notes.
Finally, best wishes!