About this blog

For a long time I never had a fixed place to write. WeChat moments, chat windows, drafts scattered across platforms — once written, it all sank, and six months later I couldn't even find a paragraph I knew I'd written. This blog starts there: a stable URL that can be indexed, re-read, and pointed back to years from now.

Who it's for

The first reader is future me. If a post still feels useful when I come back to it six months later, it earned its place.

The second reader is anyone doing similar things — writing their own code, building their own tools, running their own projects. If something is only useful to me for one week, a private note is enough; it only goes here when I think it might save someone else a detour.

What I'll write

• AI coding and document-driven development. I use AI tools to write code every day but have never sat down to put the method on paper. I'll write what actually worked when run for real, including the parts that failed.
• Personal project retrospectives. End-to-end: idea, technical choices, launch, maintenance, and the moment I walked away. Even when a project doesn't make it, the judgment along the way is worth keeping.
• Trade-offs in tools and workflow. Not a "best tools of the year" roundup. Why I kept this tool, why I dropped that one, when going manual was actually faster.
• Longer-term thinking. Every few months, a step back to look at direction, efficiency, and pace. Less about conclusions, more like a letter to myself.

What I'll skip

• Chasing industry hype. I'd rather use it, hit the rough edges, and then write — no race for timeliness.
• Tutorial clickbait. "Master Y in X minutes" is exhausting to read and I don't want to make more of it.
• Filler weeklies and monthlies. If a week has nothing to say, let it pass.

Pace

No publishing-frequency target. Drafts can sit for a long time — there are already a few hiding under this site — but anything that ships should have something real in it.

Bilingual

Chinese is my native language, English is my working language. I'll write each side once instead of mechanically mirroring sentence structure, so Chinese reads like Chinese and English reads like English. When a translation isn't done yet, the language switch goes grey rather than falling back to the wrong language.

About this post

A post about the blog itself is a little self-referential. I'm leaving it here as an anchor: if some day I find this place chasing trends or traffic, I can come back and remember what it was actually for.