Yesterday, of occupation, life, and sideline in . Today, I will focus on summarizing the learning and sharing of technology last year, and then plan for the next 2022 plan.
0. Let’s start with blogs and videos
I will organize and share the things I have done recently on the blog, so reviewing the blog posts can review most of the technical work I did last year.
Step on the pit to share | Avoid wrong next time | 3 |
JS details exploration | I didn’t know before, but after exploring | 3 |
New technology exploration | Explore other non-JS technical content | 11 |
webpack+babel+esbuild+swc | Front-end tool chain | 9 |
notes | Scattered notes | 2 |
Common technology sharing | Technology-related sharing, mostly known content | 7 |
Push book, push video | Recently seen books and own videos | 3 |
Video, application creativity | Suddenly think of something that can be done | 3 |
industry analysis | 2 | |
Tool usage sharing | Various tools related | 9 |
Water Recruitment Notice | (The water is a bit too much... | 4 |
Life sharing | 5 |
In terms of video, I stumbled upon CloudStudio.net , which I think is quite suitable for basic teaching for new students, so I made some full-stack development content based on CloudStudio, such as Express.js slice uploading large files, etc.
Last year, I insisted on the live broadcast for more than half a year, and a lot of content was recorded in it, but it has not been sorted out yet. I hope this year I will have the opportunity to sort out and release it.
1. Technical keywords for 2021
In October 2021, I left OpenResty and joined Jinshan Office. So my technical route can also be clearly divided into two stages.
1.1 OpenResty
This year's main work is Showman, and I hope to turn it into a useful and usable SaaS product that can complete video recording, document generation, and Navlang development and debugging. So this year, I first studied how to use VNC display to record video and edit under Linux environment. During the period, Navlang was constantly updated, and the details of the use of JS were studied in depth.
The main technical keywords during OpenResty are as follows:
- FFmpeg
- node.js
- Linux/VNC
- Asynchronous function and try...catch...
- new Function() vs eval()
- Upgrade to webpack@5
- height:100% and flex:1
1.2 Kingsoft Office
Later, I went to work at Jinshan. This experience was quite bad. I suggest those who want to go to think twice. During this period, I mainly researched and developed scaffolding upgrades and code static analysis. The keywords are as follows:
- sonarqube
- webpack => esbuild
- babel => swc
- pnpm
1.3 Other
Technologies not mentioned above are listed here:
- Chrome Extension MV3
- TypeScript
- Vue3 + <script setup>
- Docker
2. Content self-recommendation
Continue to select three articles from last year’s blog to recommend to everyone:
- talk about remote work again, mainly for the boss’s reference
- Chrome Extension Manifest V3: Design Principles
- Understand job hunting from the employer’s perspective
I made a lot of videos last year, and I recommend a small series:
3. Technology development in 2022
Now I have left Jinshan office and am looking for my next job. Without the constraints of technical debt, I can choose the next technical direction more freely. The tentative goals are as follows:
- Vue3 + TypeScript
- Vite
- pnpm
- Docker
- Cucumber + Cypress.js
4. 2022 Sideline Development
In addition to the main business, continue to develop side businesses, not to make money, to make friends.
- Participate in more industry activities, such as hackthon, meetup, workshop, etc.
- Make some local meetups and workshops by yourself
- Continue to do live broadcast and video recording
- Develop several open source projects
5. Summary
In any case, after bidding farewell to OpenResty, my career will usher in a new turning point. 2022 must work hard. Let's cheer together.
This article participated in the SegmentFault essay "2021 Summary" , and you are welcome to join as well.
Simultaneously posted on my blog: a new turning point in career, 2021 technical summary , welcome to leave a message for discussion.
**粗体** _斜体_ [链接](http://example.com) `代码` - 列表 > 引用
。你还可以使用@
来通知其他用户。