Blog Migration

 It has gone about 5 months since I wrote blogs last time. During this time, I spent most of my time at work. Even if I’m free, I didn’t spend much time to make up for the lack of knowledge. It wasn’t until last month, around mid-April, that I gradually wanted to get rid of this state. So I stated from the areas that interests me. Next, let me review what happened in the past months.

Cause

 Since I graduated and worked nearly half a year ago, in addition to daily entertainment, I often browse GitHub, go out for dinner with friends, or play ‘World of Warcraft’ online with classmates, etc. But I always felt like something was missing. After they started working and going to school, they had less and less time for dinner and entertainment together.

 Although I can study new things in daily work, I feel still lacking. Later I realized that It was probably because I didn’t take enough action and was consumed by the anxiety on the Internet. I gradually realized that if I continued like this, I would never live up to my expectations.

Migration

 I have been considering migrating my blog since the beginning of May. It’s necessary to consider the following aspects when migrating my blog:

1. Lower learning cost
2. Reusable
3. Indirect or direct access to areas of interest
4. Framework stability

 After comprehensive consideration, I finally chose the hugo framework. On the one hand, hugo is widely used. In addition, I may use Golang when exploring network knowledge in the future. It just so happened that hugo was developed using the Golang.

 Next, I need to choose a nice theme. However, Hugo has less reference documents than Hexo. So at first, I considered hugo-theme-bootstrap Because its Chinese documents is well written and supports both blog and document layouts. However, there are not many participants, and the author may not maintain it for a long time, so I didn’t adopt it in the end. Later I adopted hugo-theme-stack, it has almost no third-party dependencies, and the Chinese document is relatively complete.

 After improving the overall layout and some details, I spent half a day thinking about Github Actions. I had used Jenkins to build before, but this time I was struck on the authentication of the deployment public key. Finally I solved it.

Planning

 I should reflect on the fact that I didn’t stick to most of the plans I made in the past (such as improving English, learning FPGA and circuit knowledge, exploring computer networks, etc.).

 Among them, I really couldn’t stick to improving English, so I simply learned English by supporting multilingual articles; As for computer networks, I often debug LWIP at work, and often toss around on cloud servers and local nas in my life. I may participate in related open source projects in the future; When it comes to hardware-related things, I feel a headache, but since I will use it in my future work, I plan to learn the development board I bought; In addition, I also need to understand the new rust language (communicate with colleagues), learn Linux development, learn 408… It’s such a headache that there are too many things I want to do.

 Combining interests and work, I need to improve my blog, explore computer networks, learn FPGA and circuits, and find time to understand the rust language.

2024-06-17 First update