写作方法2013tiledtext.com
Tiled Text：一种不同的文本编辑方式
Show HN: Tiled Text – a Different Approach to Editing Text
导读
这是一款名为 Tiled Text 的文本编辑器，它尝试用不同于传统纯文本的方式来编辑文本（更偏结构化/分块）。对写作者来说值得一读：评论里讨论了编辑工具真正的效率瓶颈在哪里、结构化编辑的好处，以及“编辑过程中必然出现半成品结构”这一现实问题，能帮你反思自己的写作与修改流程。
可以直接用的写作要点
- 01
挑写作工具时优先看能减少重复操作的功能（多光标、快速跳转），它们比炫酷的可视化更能省时间。
- 02
把内容按更高层的结构而非纯文本来组织，能减少格式和琐碎排版决策的负担。
- 03
好的写作流程要能容忍“半成品”状态：编辑过程中结构暂时不完整很正常，别逼自己一次到位。
- 04
真正的瓶颈往往在“输入/大量产出”这一环，先解决它，再去优化整理和搬运已有内容。
HN 评论精选
高效编辑（多光标、快速跳转）最省时间，但作者更想要语义级的重构能力，而不是花哨的可视化。
我喜欢人们开始探索文本编辑的替代方案，比如 Light Table 就有一些好想法。对我来说，Sublime Text 的多光标和快速符号跳转大大节省了时间。我从不觉得需要代码折叠、小地图或符号侧栏，我真正想要的是更高效的编辑。比如这类编辑器完全没有语言敏感的“重构”支持，我无法重命名变量/方法或提取方法，连“选中当前整个嵌套层级”这种简单操作都没有。我不确定这个具体方案是否只对小众有用，但它看起来很漂亮，祝好运！
lobster_johnson查看英文原文
I like the way people are starting to look at alternative approaches to text editing. Light Table has some good ideas, for example. For me, multiple cursors and fast symbol navigation in Sublime Text has been a huge time saver. Personally, I have never needed code folding (I prefer to have my own map of the code in my head, and anything that obscures that map just gets in the way), or Sublime Text's minimap, nor have I ever needed the symbol sidebar that is found in some IDEs (Eclipse, Netbeans). What I really want is more efficient editing. For example, text editors like Sublime have zero language-sensitive refactoring support. I can't rename (variables, methods etc.) or extract methods, for example. Even some really simple operations like "select entire current nesting level" are unavailable. I remember using Eclipse 7 years ago and really liking the intelligence of the incremental compiler backend, even though I hated Java; it seems that with backends such as Clang, those tools can once again be applied outside big, annoying IDEs like Eclipse and Xcode. Not sure if this particular approach is useful except to a small niche, but it looks pretty slick. Good luck with the effort!
搬运已有内容容易，真正的难题是从零大量产出；瓶颈在输入方式本身。
这是个很酷的玩具，但似乎没有解决在触屏设备上写代码的主要问题：在触屏上打字很糟。移动代码并不难——拖动高亮、抓住它移到别处，你做得优雅。但在没有传统键盘的设备上写大量代码很糟糕，这才是难题。在它被解决之前，没人能说自己在无键盘设备上开发取得了真正进展。
ebbv查看英文原文
This is a cool toy but it doesn't really seem to address the main issue of writing code on a touch device; typing on a touch device sucks. Moving code around is not a difficult problem to solve. Drag to highlight, grab it and move it somewhere else. You've done that elegantly. But writing massive amounts of code on a device without a traditional keyboard is awful and that's the difficult problem to solve. Until that's solved I don't think anyone can claim to have made real progress enabling development on keyboardless devices.
更高语义层/结构化存储很有价值，但工具必须能容忍编辑过程中“未完成、暂时不合法”的中间态。
我希望看到更多在比纯文本更高语义层上操作的编辑器/IDE。最大的问题当然是与现有语言/开发生态互操作。我曾设想过一种语言或平台，内部一切都以某种 AST 存储，文本只是其中一种表示。这至少能一劳永逸地解决编码风格（至少格式部分）：每个人维护自己的类 CSS/XSLT 转换，tabs 或空格、括号分号随喜好。我见过一些“结构化编辑器”研究项目，只允许语义正确的输入。除了投入精力外，我能看到的主要问题是如何处理不完整的文档，因为几乎任何创建或编辑过程都会有临时的非法结构；Emacs 的 paredit 如果你不用它的专门操作、试图以破坏结构的方式编辑代码，就会相当令人抓狂。
shabble查看英文原文
I'd love to see more editors/IDEs that operate at a higher semantic level than plain text. The biggest problem is of course interoperating with existing language/development ecosystems. I have pondered in the past about a language or platform where everything is stored internally as some form of AST, and text is just one of the possible representations. It would at least solve the coding-style (well, the formatting part at anyway) issue for once and for all; everyone just maintains their own CSS/XSLT-alike transforms with tabs or spaces and brackets and semicolons wherever they like. I've come across occasional research projects in 'structural editors' which only allow semantically correct input (and, depending on the size of the input alphabet, can function through almost 100% autocomplete menu input) Anastasia[1] is one that I know of, and this Modeless Structure Editing by Sufrin et al.[2] looks interesting. The main issue I can see, apart from the effort involved, is how to deal with incomplete documents, since almost by creation or editing process will have interim invalid structures. Emacs paredit can be pretty infuriating if you don't use its specialised operations and try to edit your code in a way that malforms the structure. [1] http://dream.inf.ed.ac.uk/projects/anastasia/ [2] http://www.cs.ox.ac.uk/bernard.sufrin/edit.pdf
同类还值得读
被低估的工程技能：把文章写好
Undervalued Engineering Skills: Writing Well
这篇文章讨论为什么“写得好”是被低估的工程能力，以及它如何在团队协作、系统设计和职业发展中持续带来回报。
写作方法2019 · 1,109 分 · 371 评4 条写作要点编辑精选每行只写一句话：让写作和修改都更轻松的排版法
Writing one sentence per line
这是 Derek Sivers 的一篇短文，主张写作时每行只放一个句子，而不是按段落排版。
写作方法2022 · 849 分 · 297 评4 条写作要点编辑精选书面沟通是远程工作的超级能力
Written communication is remote work super power
这篇文章讨论远程工作中书面沟通的价值，评论区则补充了异步与同步沟通的适用场景，并提醒读者：备忘录、结论先行、结构化命令格式等书面沟通传统早已有之。
写作方法2020 · 831 分 · 190 评4 条写作要点编辑精选如何写出有用的文字
How to Write Usefully
保罗·格雷厄姆在这篇文章里给"有用的写作"下了一个可操作的公式：有用≈重要×新颖×正确×清楚，任一项为零，整篇文章就等于零；他还主张敢下确定判断、删掉让自己心虚的句子。
写作方法2020 · 821 分 · 285 评4 条写作要点编辑精选如何写得更清楚、想得更清楚，并学会复杂材料（PDF）
How to write more clearly, think more clearly, and learn complex material [pdf]
这份 PDF 讨论如何把文章写清楚、把思路理清楚，并用写作来学习复杂材料。
写作方法2022 · 779 分 · 153 评4 条写作要点编辑精选