惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

G
GRAHAM CLULEY
S
Security @ Cisco Blogs
P
Proofpoint News Feed
Cisco Talos Blog
Cisco Talos Blog
D
Darknet – Hacking Tools, Hacker News & Cyber Security
C
Cyber Attacks, Cyber Crime and Cyber Security
T
Tor Project blog
WordPress大学
WordPress大学
Project Zero
Project Zero
S
Schneier on Security
P
Proofpoint News Feed
小众软件
小众软件
P
Privacy International News Feed
美团技术团队
L
LangChain Blog
Know Your Adversary
Know Your Adversary
J
Java Code Geeks
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
The Register - Security
The Register - Security
N
Netflix TechBlog - Medium
Microsoft Security Blog
Microsoft Security Blog
Engineering at Meta
Engineering at Meta
I
InfoQ
量子位
Vercel News
Vercel News
博客园 - 三生石上(FineUI控件)
Spread Privacy
Spread Privacy
D
DataBreaches.Net
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
U
Unit 42
P
Privacy & Cybersecurity Law Blog
C
Cybersecurity and Infrastructure Security Agency CISA
T
The Blog of Author Tim Ferriss
Latest news
Latest news
K
Kaspersky official blog
MongoDB | Blog
MongoDB | Blog
L
LINUX DO - 热门话题
Simon Willison's Weblog
Simon Willison's Weblog
云风的 BLOG
云风的 BLOG
S
Securelist
AWS News Blog
AWS News Blog
F
Fortinet All Blogs
T
Threat Research - Cisco Blogs
Stack Overflow Blog
Stack Overflow Blog
Scott Helme
Scott Helme
Help Net Security
Help Net Security
Y
Y Combinator Blog
宝玉的分享
宝玉的分享
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
T
Tenable Blog

Sophie Alpert

Deconstructing “services” I don’t want AI agents controlling my laptop Materialized views are obviously useful TODOs aren’t for doing Everyone is wrong about that Slack flowchart Hire me to empower and upskill your eng team How React Changed the Web Forever: A Documentary Fast and maintainable patterns for fetching from a database React Conf: “Building a Custom React Renderer” Why review code? Metrics by proxy Yak shaving and fixing Voice React Conf: “React Today and Tomorrow” Why we host conference talk dry runs React Podcast: Inside React Type errors with inference need stacks Observable programming React 16: an API-compatible rewrite Hi, I’m trans. Initializing on the main thread using dispatch_once A near-perfect oninput shim for IE 8 and 9 Using React to speed up the Khan Academy question editor What I did at Khan Academy, 2012 edition Preventing XSS attacks when embedding JSON in HTML Rolling back to an old revision in Mercurial (like git reset)
There are no lossless transformations of natural-language text
Sophie Alpert · 2026-06-25 · via Sophie Alpert

In my work at Clay I recently wrote an internal policy on acceptable use of AI writing by engineers, and I’m sharing it here. It’s my hope that one day better AI tools might be able to help us think, but until then I fear that using AI to write does the exact opposite.

Good writing is a tool to clearly communicate ideas from your brain into someone else’s.

As of 2026, AI models — despite their coding ability — are not yet at a point where their unedited output will achieve this goal; you as an author need to take the time to make sure that all of the ideas in the writing are the ideas that you personally intend to convey (including the structure and wording that determines which ideas are emphasized) and that the documents are a good use of your readers’ time.

It’s allowed to use AI tools while brainstorming or drafting your writing and certainly while proofreading, but make sure to consider the following principles while doing so:

  • You must stand behind every idea and every sentence in your docs. It is your responsibility to make sure that the entire document is representative of your own thoughts before you share it. If a reviewer asks, “What did you mean by this line?”, it’s not acceptable to reply with “Oh sorry, AI wrote that, just ignore it.” You will confuse your readers (and waste their time) if you present them things that are not genuinely representative of your thoughts. In some cases, readers will recognize and call out the incongruous parts; in others, they will be misled as to what your actual thoughts are.

  • Writing is thinking. Spending time on the writing process — on deciding what to emphasize and how to structure your ideas clearly — teaches you more about your topic. If you circumvent this process, you will probably walk away with a poorer understanding of the subject matter. In many cases, written artifacts like tech specs, project status updates, and incident retrospectives serve as a “proof of thought”. The artifact itself is not the only goal; instead, detailed thinking about the problem is the goal. Outsourcing the creation of these documents to AI (so that you can skip the thinking) risks circumventing this very purpose. Even if working with AI helps you think through a problem, you’ll understand it better if you thoroughly review the result yourself.

  • More time should be spent authoring a document than consuming it. If you generate a document from a short prompt then ask your readers to go through the longer output, you are disrespecting their time. They can always talk to ChatGPT themselves if they want to. Most docs are written by one person but are read by many people, so any extra time that readers need to spend to understand what you meant incurs a multiplicative cost on the team’s time. Conversely, if you spend extra time to make your document clear and concise before sending it, you are paying a one-time cost that every reader will benefit from.

  • Longer is not better. Pascal once wrote, “I have made this [letter] longer than usual because I have not had time to make it shorter.” AI makes it much easier to generate a long doc, and one of its strategies is to include many sentences that don’t say much at all and detract from the actual content. If you are producing a longer piece of writing from a shorter prompt, consider instead just sharing the prompt itself. If you use AI to edit without lengthening, vacuous sentences are less of a risk but your meaning may still get obscured.

    There are no lossless transformations of natural-language text — every rewrite and rephrase changes the meaning of your writing, and if this is done by an entity that doesn’t have the most detailed mental representation of what you personally were trying to communicate, information will be lost. Readers will appreciate hearing your thoughts, even at the expense of supposed “polish”.

It’s also OK to quote AI generations verbatim that don’t meet the above standards if you mark them clearly as such. Sometimes it’s useful to say like “Claude offered this idea, do you think it’s worth looking more into?”, and this is allowed.

As AI tools improve over time at theory of mind and get better at writing, it may make sense to lean more heavily on them, but the principles above will remain important.