To be honest, I do not know.
I still cannot fully explain what a personal technical information site should carry.
It is not simply a blog.
It is not a resource site.
It is not only a project portfolio.
If I have to find a nearby description, it is more like a small bookstore, and also like my own gallery.
Inside are things I chose, wrote, and created myself.
Articles, materials, images, project traces, paths for solving problems, and some thoughts that are not easy to classify.
They may not be perfect.
They may not be professional enough.
In other people’s eyes, they may only be ordinary records.
But everyone has their own way of thinking, right?
Everyone has ideas, and everyone has stories.
My story will stay here.
There is a little gentle idealism in this. It is not for immediate monetization, not for looking impressive, and not for pleasing anyone’s recommendation system.
It is only because some things feel worth placing here.
Journal
The journal section should hold essays and thoughts.
Not daily logs, and not proof that my life is especially exciting.
It is more like things that have settled down in the mind.
Some are emotions, some are judgments, some are understandings of life, and some are only a sentence that suddenly appears late at night.
These pieces may not be useful.
They may not be able to become any kind of method.
But they can leave behind a person’s state.
How a person thinks, how tired they are, how they organize themselves, and how they understand the world during a certain period.
That is the value of the journal.
Technology
Technical content, to me, does not always have to be a tutorial.
I also do not want to write it as something that makes people learn everything after reading it once.
There is too much technology. It is impossible to learn everything, and impossible to write everything. Many times, a person only encounters a problem and then tries to solve it.
So the technical articles here are more like records of one possible path.
What problem did I meet?
What was I thinking at the time?
What did I look up?
What did I try?
What direction finally solved it?
It may not suit everyone, and it may not be the most standard answer. But at least it is a path that has been walked. After seeing it, someone may not copy it directly, but they can know: this problem can be thought about in this way.
That is enough.
Technical writing does not always need to pretend to be authoritative.
It can be more honest.
It can write the process of solving, the route of thinking, the mistakes encountered, and why a certain choice was finally made.
Projects
Projects should not become a collection of tiny updates.
If every small change becomes a project record, the section will quickly become fragmented and tiring.
Projects are better for whole things.
A system.
A tool.
A long-term idea.
Or something that shows the path from idea, to process, to result.
I care more about the process than only displaying the result.
The result matters, of course. But if only the finished piece is placed there, it easily becomes an empty display. Like a portfolio with only a beautiful cover and a few lines of introduction, it may look complete, but you cannot see how it grew.
I hope the project section can show some thinking.
Why make it?
How did it begin?
What problems appeared in the middle?
How did it change later?
It may not be perfect in the end, but it has a path behind it.
Materials
The materials section feels a little like exhibits and references in a gallery.
It is not simply a download site, and it is not for piling up images.
Materials should explain their source, usage, and boundary.
Why does this image appear here?
Where is it used?
Can it be quoted?
Was it made by me, generated with AI, or taken from somewhere else?
If these things are only hidden inside code, other people cannot see them. But if they are organized, they change from “files behind the website” into a visible part that can be looked at.
When someone looks at a website, they do not only read the articles.
Sometimes they also look at how it chooses images, organizes materials, and places visuals together with text.
That is also a form of expression.
Like a Small Shop
So what should this site carry?
I think it does not have to carry something very grand.
It is more like a small shop.
It has a slight curator feeling.
Not an authority, not a successful person, and not a marketing account.
Only a person organizing the things he thinks are worth leaving behind and placing them on the shelves.
Someone can come in and take a look.
If they find it useful, they can take away a little thought.
If someone only passes by the door, that is fine too.
It exists, but it does not draw much attention.
It does not need to pull every passerby inside, and it does not need to turn every article into material for spreading.
It first exists here.
Like a small bookstore, and also like my own gallery.
Inside are things I chose myself.
