> For the complete documentation index, see [llms.txt](https://book.funcd.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://book.funcd.org/wen-zhang/posts/life/why-i-write.md).

# 我为什么还在写博客

> `方法论` · `随笔` · 2026-07-27

## 起因

排查一个线上问题，翻到自己两年前的笔记，里面写着同一个报错、同一个原因、同一个解法。当时的我显然彻底忘了这回事，正准备从头再查一遍。

那一刻很清楚地意识到：**没写下来的经验，等于没有过。**

## 写作是一种压力测试

口头解释一件事可以含糊过去——听的人会自动补全，你也就以为自己讲明白了。写下来不行。落到字面上的每一步都要成立，写到一半卡住的地方，往往就是理解真正的断点。

这几年最有价值的几篇文章，都是这么来的：本来想记录一个已知的解法，写着写着发现自己讲不通某一步，回头再查，才找到真正的原因。**没写就不会发现这个洞。**

## 三条自己定的规矩

**只写做过的事。** 转述别人的结论没有意义 —— 那是搬运，不是记录。写自己动手做过的，哪怕小到"这个 flag 我调了半天"。

**保留失败路径。** 大部分文章只呈现最终正确的方案，读者却卡在那些"看起来对但不对"的岔路上。所以我尽量写清楚：我先试了什么、为什么不行。绕过而非根治的方案，明确标成 workaround，不假装是解法。

**允许改。** 写下来的东西不是碑文。结论过时了就改正文，重要的修订记进 [更新日志](/guan-yu/changelog.md)。让读者读到一篇正确的文章，比留一篇带勘误的旧文有用。

## 关于读者

这个博客几乎没什么流量，我也不打算做什么增长。

如果一定要设想一个读者，那是**三个月后的自己** —— 已经忘光了细节，正在半夜对着同一个报错发呆。为这个人写，标准反而更高：他不吃"显然"和"众所周知"这一套，因为他真的不知道。

偶尔有陌生人因为一篇文章少踩一个坑，那是意外之喜，不是目标。

***

*后续想法会追加在这里。*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://book.funcd.org/wen-zhang/posts/life/why-i-write.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.