getting it access to data is important too, add in the gmail, google calendar, etc. connectors but I think people underestimate how much context they have in files
让它获得数据访问权限也同样重要，把 Gmail、Google Calendar 等 connector（连接器）也加进来，但我觉得人们低估了他们在文件里 actually 拥有的 context（上下文）有多少。
- image or video editing? write scripts - finances, tax work, etc? put in PDFs, write scripts, output HTML - medical advice? put in PDFs + data, output HTML - filling out paperwork? write scripts - creating a report? write HTML - making plans? write HTML
- 图片或视频编辑？写 scripts（脚本） - 财务、税务工作等？放入 PDF，写 scripts，输出 HTML - 医疗建议？放入 PDF + 数据，输出 HTML - 填写文书表格？写 scripts - 制作报告？写 HTML - 制定计划？写 HTML
the basic trick to using Claude Code for non-technical work is to put a bunch of files in a folder and tell it can write scripts + make HTML
使用 Claude Code 处理非技术性工作的基本窍门是：把一堆文件放进一个文件夹里，然后告诉它可以写 scripts（脚本）并生成 HTML。
continuing my HTML era, I had so much fun talking with Claire at Code w/ Claude about staying in the loop with long running agents
继续我的 HTML 时代，我在 Code w/ Claude 和 Claire 聊如何在长时间运行的 agent（代理）执行过程中持续掌握进展，聊得特别开心
okay this is going kinda viral and tbh my original text was kind of messy, so here's a second pass with the help of Claude: -- Implement <SPEC>. As you work maintain a running implementation-notes.html file that captures anything I should know about how the implementation diverges from or interprets the spec, including: - Design decisions: choices you made where the spec was ambiguous - Deviations: places where you intentionally departed from the spec, and why - Tradeoffs: alternatives you considered and why you picked what you did - Open questions: anything you'd want me to confirm or revise
好吧，这条内容有点要 viral（爆火）了，说实话我原来的文本也确实有点乱，所以这是在 Claude 帮助下整理出的第二版：——实现 <SPEC>。在工作过程中，持续维护一个 implementation-notes.html 文件，记录任何我需要了解的、关于实现如何偏离 spec（规范）或如何解释 spec 的内容，包括：- Design decisions（设计决策）：当 spec 存在歧义时你做出的选择 - Deviations（偏离项）：你有意不按 spec 来实现的地方，以及原因 - Tradeoffs（权衡）：你考虑过哪些替代方案，以及为什么选择现在的做法 - Open questions（待确认问题）：任何你希望我确认或修改的事项
as much as you spec there are always still ambiguities and unknown unknowns that come up and this gives the model a good out to make decisions but keep you in the loop
不管你把 spec 写得多详细，总还是会出现各种歧义和未知中的未知，而这样做能让 model（模型）在做决策时有一个很好的出口，同时又能让你始终 stay in the loop（掌握进展）
tired: I brought my work laptop and my personal laptop wired: I am dual wielding
累了：我带了工作 laptop 和我的个人 laptop，有线连着：我这是在双持呢
I've been using HTML for planning, speccing, exploration, code review, reports and a lot more.
我一直在用 HTML 来做规划、编写 spec（规格说明）、探索、code review（代码审查）、报告，以及更多事情。
Jarred tried rewriting Bun in Rust and it passes 99.8% of the existing test suite we're not being ambitious enough
Jarred 试着用 Rust 重写 Bun，而且它通过了现有测试套件的 99.8%，我们还不够有雄心。
You can also see example HTML documents I've generated here:
你也可以在这里查看我生成的一些示例 HTML 文档：
HTML is the new markdown. I've stopped writing markdown files for almost everything and switched to using Claude Code to generate HTML for me. This is why.
HTML 是新的 markdown。对于几乎所有内容，我已经不再编写 markdown 文件，转而使用 Claude Code 为我生成 HTML。这就是原因。
[1]
"everyday we're trying to obtain more compute to pass on to you, we're sorry if it takes sometime but we're going to acquire as much as we can" you heard the man
“每天我们都在努力获取更多 compute（算力）来提供给你们，很抱歉这可能需要一些时间，但我们会尽可能多地获取。” 你已经听到他本人这么说了。
my white whale is when CC sometimes looks like it hangs during big file writes, I think we found it 😭
我一直苦苦追查的问题是：CC 在写入大文件时有时看起来像是卡住了，我觉得我们找到原因了 😭
a big part of this is we're working on making the no flicker renderer excellent so we can ship it as the default renderer, more updates coming there but lots of other papercuts coming
这件事很大一部分原因在于，我们正在努力把 no flicker renderer（无闪烁渲染器）做到非常出色，这样就能把它作为默认 renderer（渲染器）发布；这方面还会有更多更新，不过也还有很多其他烦人的小问题在陆续处理
we're doing a lot more of this, hunting down some of the most annoying bugs in Claude Code let me know if you have any white whales
我们正在做更多这类工作，追查 Claude Code 里一些最烦人的 bug（缺陷）；如果你也有自己一直苦苦追查的问题，告诉我吧