写作与思考2022news.ycombinator.com编辑精选
打字时我觉得自己更笨，手写时觉得自己更聪明
I feel dumb(er) when typing, and smart(er) when writing
导读
作者发现自己打字时思路容易卡壳，改用纸笔把问题写下来往往几分钟就理顺了，于是发帖求证这是不是普遍现象。评论区把它归结为「切换场景」和「写作逼你想清楚问题」两件事：动手写代码属于解空间，而纸笔和长文更擅长梳理问题空间——这正是写作者值得读的地方，写作不只是表达，更是思考的工具。
可以直接用的写作要点
- 01
卡住时先别急着改方案，换一种媒介（纸笔、白板、口述）把问题重新讲一遍，往往就能突破僵局。
- 02
在动笔解决之前，先用文字把问题本身写清楚：问题的边界、约束、你已经知道什么，别一上来就写解法。
- 03
把长文写作当成思考的正式环节（比如亚马逊的备忘录、开源项目的 RFC），逼自己把问题想透彻，而不是只写提纲或幻灯。
- 04
手边常备一个本子，允许自己在思考时随手涂画，这种低成本的「乱写」常常是想法成形的触发点。
HN 评论精选
把「换媒介」理解为通用的场景切换，用来打破卡壳状态。
切换场景对换视角、突破卡点特别有效：从屏幕换到纸笔是一种，换到白板也行，找同事口头讲一遍、对着橡皮鸭讲、出门散步也都行。关键是要学会识别自己已经卡住、毫无进展甚至陷入「习得性无助」的状态，然后主动改变环境来打破它。
PragmaticPulp查看英文原文
Context shifts are actually great for changing your perspective and reinvigorating your ability to work around road blocks. Switching from screen to paper is one way of context shifting. You could also switch a whiteboard. You could switch to talking through the problem verbally with a colleague or, lacking that, a rubber duck. You could just get up and go for a walk to think about that problem. Context shifting from indoors to outdoors can be a significant change. It helps to learn how to recognize when you’re stuck, not making any progress, and have maybe a bit of “learned helplessness” slowing you down even further. Shaking up your context can help break out of it.
长文写作是逼自己想透问题的制度性方法。
写作是思考问题最好的方式，它需要专注和投入。贝索斯说亚马逊做过最聪明的事之一，就是禁止低质量的演示文稿，要求每次会议都写长文简报，确保会议发起人把问题彻底想清楚，团队也能在前 30 分钟认真读完。开源界的 RFC 流程也是同理（Rust、Python、JavaScript、C# 都在用）。知识工作里 80% 是解决问题和创造性思考，只有 20% 是写代码；我职业早期总是直接写代码，现在则把写代码放到最后。
thenerdhead查看英文原文
Writing in my opinion is the best way to think through problems. It takes concentration and effort. Jeff Bezos says the "smartest thing" they did at Amazon was to ban low effort presentations and embrace writing long-form briefs for each meeting. That made sure the problem was thoroughly thought out by the meeting owner and is read by the group in detail for the first 30 minutes of the meeting. In open source, many projects adopt a RFC(request for comments) process in which a problem is written about exclusively with solutions and asking for public feedback. This works effectively in ecosystems like Rust, Python, JavaScript, and C#. If you think about knowledge work in general, 80% of the job is problem solving, creative thinking, etc. 20% of the job is implementing / coding. Jumping straight to code was something I did when I was early in career, but now it's the last thing I do until I understand the problem in detail.
代码属于解空间，纸笔属于问题空间，别过早进入解空间。
要区分问题空间和解空间。写代码（大多数语言）本质是在解空间里表达，很不擅长讨论问题空间。我发现多数人太早打开编辑器，问题还没分析透就开始写解法。我从编辑器转回纸笔，通常意味着我难以把正在写的代码对应到问题的某一部分，于是先回去把问题探索清楚再写解法——我猜你的情况也差不多。
pdpi查看英文原文
It's useful to understand the difference between problem space and solution space. Writing code (in most languages) is all about writing in solution space, and sucks at talking about problem space. I find that most people tend to jump into their editor way too quickly and start writing the solution before they've thoroughly analyzed the problem. When I jump from editor to pen and paper it usually means that I'm having trouble mapping the code I'm writing to a part of the problem Im'solving, and I switch to exploring the problem more before going back to the solution. I'm going to go out on a limb and say that that's pretty much what happened to you as well.
随手涂鸦也是有效的思考工具，不该被当作摸鱼。
因为同样的原因，我电脑旁永远放着一个小本子。帮我理清问题、挑方案的不只是写，还有涂鸦：一边想一边随手画，有时能让事情突然对上、冒出新的想法。我第一份游戏工作时，主管对我偶尔在电脑前涂本子有意见；其实我并不是整天涂鸦不干活，每次只是思考任务或问题时涂几秒到几分钟。那次之后我很久都不敢在工作中涂鸦，这对我和我的工作都是损失。
drakonka查看英文原文
There's a little notebook by my computer at all times for this reason. It isn't even just writing that helps when I'm trying to figure out a problem or pick a good approach, but doodling. Doodling while thinking seems to help things click into place and generate new ideas sometimes. In my first job in games, my lead at the time took issue with seeing me occasionally doodle in a notebook in front of my PC. It wasn't a case of sitting there doodling all day and getting no work done, or not focusing. I'd only do it for a few seconds or a couple of minutes at a time, when thinking through a task or problem. After that interaction, I stopped doodling at work for a long time, to my (and I believe my work's) detriment.
同类还值得读
不要想好再写，要写来思考
Don’t think to write, write to think
这篇短文主张不要把写作当成思考完成后的记录，而要把写作本身当作思考的工具：动笔的过程会逼出想不清楚的地方。
写作与思考2022 · 553 分 · 145 评4 条写作要点编辑精选写作即思考：学会自信地写作
Writing Is Thinking: Learning to Write with Confidence
这是一篇讲“写作即思考”的博客：作者认为写作不是把想好的东西誊写出来，而是借助写作本身把想法想清楚，因此写作者应当建立信心、敢于先写烂稿。
写作与思考2019 · 529 分 · 83 评4 条写作要点编辑精选如何用写作来思考
How to think in writing
这篇文章讨论的是「用写作来思考」：作者认为写作不只是把想清楚的东西表达出来，更是想清楚本身的工具——文字落在纸上，你才有机会看见自己思路里的跳跃、含混和漏洞。
写作与思考2024 · 424 分 · 120 评4 条写作要点编辑精选写作，帮你逃离默认的人生设置
Write to Escape Your Default Setting
文章的核心主张就写在标题里：写作是帮你逃离「默认设置」的手段——日常的思维和表达都有惯性默认的默认模式，而落笔能逼你跳出来，重新看清自己到底在想什么、要说什么。
写作与思考2025 · 407 分 · 93 评4 条写作要点编辑精选写作就是思考
Writing is thinking
文章以“写作即思考”为题，讨论写作不只是把已有想法记录下来，而是帮助澄清、组织和推进思考的过程。
写作与思考2025 · 330 分 · 128 评4 条写作要点编辑精选