Every guide to de-AI-ing a draft hands you a list of words to delete. That list starts expiring the day it ships: naming a tell is what kills it. Underneath it sits the failure no list touches — the draft commits to nothing. So I built an editing skill that fixes that one first, and put it on GitHub.
Before
In today's fast-paced development landscape, it's worth noting that observability has become paramount. Our latest release introduces a robust set of enhancements to the query planner, which now seeks by trace ID rather than scanning every span in the window, reducing median trace lookup from 4.2s to 380ms and empowering teams to delve into their traces with unprecedented clarity.
After
Median trace lookup went from 4.2s to 380ms. The old query planner scanned every span in the window; the new one seeks by trace ID first. If you page through traces during an incident, you will feel it.
Every number and every mechanism in the second version is in the first. The edit cut what was standing in front of them.
The list dies because someone published it
When delve, intricate and showcasing were publicly named in early 2024, their frequency in arXiv abstracts began falling around March — before GPT-4o shipped that May. Writers killed those words, not a model update. Meanwhile significant and additionally kept climbing, because nobody had named them (Geng and Trotta, ~1.29M abstracts).
So a list you can read today is already decaying, and nobody can tell you how fast: the diffusion timelines that circulate as fact have no source behind them.
What doesn't expire
Across seven instruction-tuned models and five registers, every model's distribution of 67 lexico-grammatical features sits outside the human-to-human confidence band. Reword the prompt and the absolute distance moves; the ranking does not, at correlations of at least 0.985 (Nieth et al.).
"Write more casually" does not reach the thing that is broken.