Yokaze

In the second grade of middle school, I learned HTML+CSS, data analysis and algorithms, MySQL and other code-related courses. And just on the Chinese New Year's Day in 2020, I used the free static site hosting platform Netlify, cooperated with Github, and used CI deployment to launch my first online website.

At that time, I was participating in a professional team competition, where each team member had different roles, and we needed a lightweight communication bridge that could send text messages and files. Later, I spent half a month using PHP to create a lightweight web chat room based on Ajax, which could also persistently store data in a cloud virtual machine environment.

One day, I participated in a competition that changed my way and attitude towards learning. There are many technology stacks used in the competition rules, and the competition documents are filled with professional terms and development tools that have never been heard of. A complex front-end and back-end separation project development process is required: Swing GUI desktop application (Java) development, Vue2+Spring Boot front-end separation CMS management system development based on Ruoyi, interface testing, product prototype design, etc. Time was tight and I needed to learn what I needed. Before the competition, I started to learn how to use phpstudy to build a back-end development environment, configure and use Maven, JDK, and IDEA (I also needed to solve problems similar to the compatibility of JDK and Maven versions), get in touch with Redis, and the Zoyi low-code development platform... In the end, I relied on constantly learning relevant courses on the Internet, and I was successfully shortlisted in the preliminary round, but I failed to achieve good results in the subsequent semi-finals. I deeply lamented that I was too insignificant in the real world, and I began to rethink the development path that suited me.

In order to deploy the dynamic website I had developed, I could no longer rely solely on free static site hosting services, so I began looking for a low-cost solution. Later, I discovered cloud virtual hosting: an online hosting service that divides a physical server into multiple virtual servers for 'static resources' or 'PHP projects.' It is inexpensive, and sometimes even free, but its drawbacks are also very apparent—unstable network connectivity, insecure data, and poor performance.

A milestone! I have learned about Nginx reverse proxy, DNS resolution, and applying for & renewing SSL certificates, and I chose Alibaba Cloud as my domain registrar, registering one subdomain after another. I plan to continuously develop a series of projects under this domain in the future, such as setting up a personal blog, developing multiple complete project websites, and offering services. This top-level domain will be my first anchor on the Internet.

During my previous experience using cloud shared hosting, as the business grew and due to the limitations of the backend development language (only PHP environment), I started to encounter various restrictions. Shared resources meant that the performance of my website could be affected by other users, and there were certain limitations in terms of resource expansion and custom configuration. After switching to a cloud server and getting acquainted with the full Linux operating system, I experienced many significant advantages and the convenience of deploying a wide variety of backend programs. Having a public IP and dedicated resources allowed me to provide a more stable and faster service to my users. Whether handling high concurrent requests or running resource-intensive applications, the cloud server could manage them effortlessly. I actually deployed and experimented with CentOS, Debian, and Ubuntu among multiple Linux distributions, and ultimately chose Ubuntu. Later, I also tried using Arch Linux and Kali on my personal machine (a fun tinkering experience).

At this moment, my personal blog has been set up! Here, I will continuously share what I have learned and thought about. This is not just a simple record and accumulation of knowledge, but also an in-depth analysis of my process and insights in solving problems. This platform is intended to manage my personal knowledge system. At the same time, I have opened up login and registration to the public, and I look forward to analyzing and discussing various technical challenges with peers, exchanging practical solutions, and realizing the shared growth of knowledge and experience.

Having had initial exposure to Vue 3, I now have a more intuitive understanding of the differences between it and Vue 2, which I used in competitions I participated in. First is the performance improvement, which is undeniable. Then there is the Composition API; compared with Vue 2's Options API, the Composition API makes code organization more flexible and modular. I can group related logic together by functionality, rather than scattering it across data, methods, computed properties, etc., which is a significant improvement for maintaining and reusing code. Overall, Vue 3 feels more modern and efficient to me. Although I might feel some confusion at the beginning due to the introduction of new concepts and APIs, I believe that once I adapt, the improvements in development efficiency and experience it brings to me and others will be very noticeable. I am confident that as I continue learning, Vue 3 will open up a new world of frontend development for me.

I collaborated with my friend Hcat on development, and used Python to build a fully functional front-end and back-end separation project. The front-end used Vue3+Pinia+Vuetify, and the back-end chose Python (Flask)+MySQL+Redis. During the development process, we gradually solved various common problems, such as database query optimization, paging query, Redis caching strategy, etc. In fact, before going online, we also conducted a separate pre-launch test. Finally, we used Gunicorn as the WSGI server, configured Nginx for reverse proxy, and successfully deployed our Flask back-end application with the front-end packaging file to the production environment. After version 1.0 of the project, we are still jointly updating and maintaining it, and have carried out a major version reconstruction, and packaged Docker images to simplify the deployment process.

I have learned about the Go language from many blogs and articles. It is highly praised for its simplicity, efficiency, and excellent concurrency performance. After experiencing it in practical development, I chose it without hesitation. I started studying Go's official documentation and improved my practical skills by learning Gorm and Gin. I firmly believe that in the future, I will be able to create unique value with Go again and again.

This month, I devoted more time to things I am interested in, such as starting to tinker with hardware (development boards), and I bought two ESP8266s and one ESP32. Afterwards, I got engrossed in learning, understanding, and practicing network penetration on the Kali operating system. During this process, I could even feel the meaning of life—continuously exploring the things I love and realizing my dreams; they should belong to the same realm.

I started continuously using languages like Python and Go to create new projects and open-sourced the code on GitHub. The open-source community is a vibrant and creative place where I can communicate with like-minded people from around the world and share my ideas and experiences with other developers. I also actively learn more and more about modern technology implementations, development standards, and project maintenance processes from many large open-source projects.

Let's stop here for now and save the progress!