---
title: "About Me, and This Blog"
pubDate: 2026-03-26
description: "An end, and a beginning. Commemorating the blog's reopening."
author: "Cloverta"
image:
url: "https://files.seeusercontent.com/2026/03/30/1xlG/rikka-manga.webp"
alt: "rikka"
tags: ["Reflections"]
---
Content translated by DeepSeek.
I've wanted a static blog for a very long time.
But I never wrote one, why?
Because I'm lazy (runs away
I first came into contact with blogs in our club's lab. At that time, the club teacher was training us in front-end and back-end development. As a freshman, my mindset was still that of a perfectly overfitted small-town exam-taker, with problem-solving skills comparable to a fully grown kiwi fruit. Adhering to the principle of "ask if you don't understand", whenever even a speck of red appeared on my computer screen (even a warning), I would run over and ask a senior what it was for.
Until I annoyed the senior.
The senior, young but already with graying hair, wearing a beige checkered collar shirt and dark blue jeans, lying in an ergonomic chair typing on a low-profile keyboard, frowned and, without turning his head, tossed out a sentence: "If you don't understand, you can copy it and search online."
Copy it and search online.
Copy it and search online.
Copy it and search online.
The senior's half-rimmed glasses reflected a festive red glow. A programmer's blush speaks louder than any words.
Copy it and search online.
This sentence echoed in my empty mind. It's no exaggeration to say that for someone like me, who had been taught by parents and teachers since childhood to "always ask if you don't understand, searching for answers is forbidden", the impact of this sentence was no less than a high-speed Fuxing train crashing into a perfectly ripe banana in the middle of the tracks.
From then on, I embarked on the path of no return, Ctrl+C and Ctrl+V-ing code.
Like many people, the first blog I encountered was CSDN. At that time, it hadn't yet scared away a hundred million tech people and was practically the white moonlight in my heart. There was even a period when seeing CSDN in search results gave me an inexplicable sense of security.
My first blog post was also on CSDN. Among the few articles I posted later, one actually reached an astonishing 30,000 reads (I know CSDN inflates data, but, but 30k, man!).
The CSDN account I registered back then
Then, as everyone knows, CSDN became more and more... bad, cramming in plaster-like ads without restraint and an increasingly ugly greed. The last straw that broke the camel's back was when someone added my communication group one day and asked me why I had changed my articles to be paid. That's when I suddenly realized that CSDN had, at some point, secretly set my articles with higher read counts to be viewable in full only by VIPs.
Setting it like that is one thing, but the key point is they didn't give me a single cent of the revenue.
At that moment, I told myself, I've had enough of this absurd platform, I'm going to build my own blog.
My initial choice was WordPress (I think this is the same for most people) because it basically requires no coding knowledge, has comprehensive features (even a bit too comprehensive), and with some panels, it can even be deployed with one click. From deployment to posting, the whole process can be done with zero code.
But the other side of high encapsulation and high integration is extremely low efficiency. First, WordPress's extremely counter-intuitive dashboard UI design. The moment I opened the dashboard, my eyes felt like they were being assaulted by Coconut Palm's advertisements. Options with no clear hierarchy were densely spread out before my eyes. At the same time, WordPress's lamentable loading speed was no different from making my already overwhelmed brain idle and block while waiting for it to load.
Maybe my brain is single-core, but I really couldn't find the theme settings at first
Every time I needed to change settings in the dashboard felt like playing Aimlab, having to click as fast as possible while also not clicking the wrong thing. Clicking wrong in Aimlab has no penalty, but clicking the wrong button in WordPress brings several seconds of hard-lock loading time.
It was the final exam period at the time. Students were busy cramming a whole semester's worth of coursework into the last week before exams. Adopting a "if it works, it works" mentality, I updated a few blog posts on WordPress.
But after that, there was no sign of blog updates for a long time. When the New Year approached, a group friend clicked on the URL and said, "Cloverta still owes a QQbot Markdown tutorial!" By the next Spring Festival, they said again, "Cloverta still owes a blog post!" By the Lantern Festival, they didn't say anything, and by Qingming Festival, there was still no sign of him.
The group friends have not seen him to this day—it seems Cloverta indeed no longer updates.
I don't know why I'm posting this image. It's cute, please send me money.
The moment that made me decide to write a completely new blog from scratch was when I saw [閉源 lib](https://ex-tasty.com)'s blog.
The first impression upon opening the blog: harmonious color combinations, clear and concise layout, fast response speed, high-quality content, and genuine passion really shocked me. At that moment, I thought:
So blogs can be this beautiful too?
So I plagiarized... ahem, I mean, I drew a lot of inspiration from [極限風味](https://ex-tasty.com)'s design philosophy. After two days of staying up late, spending over 30 hours, I rewrote this blog based on [Astro](https://astro.build/).
It's fast, lightweight, beautiful, and convenient. Compared to the WordPress theme that hadn't been updated in 4 years, it has better mobile adaptation. Although, as the first version, there are still some minor flaws not yet fixed, I will try to maintain it slowly over time.
By the way, this blog is also open source at [ClovertaTheTrilobita/SanYeCao-blog](https://github.com/ClovertaTheTrilobita/SanYeCao-blog/), and the documentation should be detailed enough. Feel free to give it a try (