humanizing-writing

Before and after: four AI-toned drafts, rewritten

Each rewrite below removes the machine habits from a draft and adds no fact the draft didn’t have. The first two start from the 2023 style, the third is all fragments and “load-bearing”, and the fourth is a single 61-word sentence. They’re read straight from the examples folder of the repository.

A short explainer passage

Before

In today's fast-paced world, paper maps continue to play a significant role in how people navigate, despite the rise of digital alternatives. It's not just a matter of nostalgia — it's a matter of reliability. Paper maps offer several key advantages: they don't require battery power, they don't depend on cell signal, and they provide a comprehensive overview that small screens often struggle to match. Moreover, studies show that paper maps can improve spatial memory and navigational understanding. Additionally, many outdoor professionals — including search and rescue teams, backcountry guides, and military units — continue to rely on paper maps as a critical backup system. Despite the challenges posed by an increasingly digital world, paper maps remain a testament to the enduring value of analog tools, and their continued relevance underscores the importance of not discarding proven technology just because something newer has arrived.

After

Paper maps are still in use because they work where phones fail. A folded map needs no battery and no signal, and it shows the whole valley at once, where a phone screen shows only the area around you. Search-and-rescue teams, backcountry guides, and military units carry one as a backup.

What changed, and why

The rewrite is four sentences shorter than the original because the original had about three sentences of content.

  • The opener ("In today's fast-paced world") and the closing formula ("Despite the challenges... testament to") are gone. Both fit any topic and say nothing about this one.
  • "It's not just a matter of nostalgia, it's a matter of reliability" became the reason itself: they work where phones fail. Nobody in the passage had said it was nostalgia.
  • "Studies show that paper maps can improve spatial memory" is cut. The draft named no study, so the rewrite has two honest options: cite the study if the writer has one, or drop the claim. Swapping in a different unnamed authority ("guides say") or a plausible-sounding mechanism would be inventing support.
  • "Moreover" and "Additionally" are gone. The sentences follow from each other without them.
  • The three groups of professionals stay. The original names three, and nothing in it suggests the list was padded.

Version 1.x of this rewrite removed the same tells and added three negated contrasts of its own ("it isn't nostalgia keeping them around", "not because they distrust GPS but because...", "a real scenario, not a hypothetical one"). It also replaced "studies show" with an explanation of why map-reading would help, which nothing in the original supported. Checklist items 1 and 4 in SKILL.md exist because of those two mistakes.

A short technical explanation

Before

Rate limiting plays a crucial role in maintaining the stability and reliability of modern APIs. It's not just a defensive measure — it's a foundational component of good API design. By implementing rate limits, engineering teams can ensure fair usage, protect backend infrastructure, and foster a more predictable system for all consumers. Additionally, rate limiting helps mitigate the risk of cascading failures, which can occur when a single misbehaving client overwhelms shared resources. Furthermore, well-designed rate limiting strategies typically incorporate several key elements: clear error messaging, transparent limits, and graceful degradation. Despite the added complexity it introduces, rate limiting remains a testament to thoughtful, resilient system design, and its importance cannot be overstated in today's increasingly interconnected digital landscape.

After

Rate limiting exists because one misbehaving client can overwhelm resources that every client shares, and the failure then spreads to all of them. With a limit in place, that client's extra requests are rejected (HTTP 429) and the others keep working. A well-designed limit returns a clear error, publishes its limits, and degrades gradually. It also makes the API more complex.

What changed, and why

  • "Plays a crucial role in maintaining the stability and reliability" is replaced by the mechanism the original gives two sentences later: one client overwhelming shared resources.
  • "It's not just a defensive measure, it's a foundational component" and the closing "testament to... cannot be overstated" are cut. Neither carried information.
  • The first list ("ensure fair usage, protect backend infrastructure, and foster a more predictable system") is cut. It says the same thing as the mechanism, three ways.
  • The second list stays at three items. The original names three properties of a good rate limit and each is a different property.
  • "Additionally" and "Furthermore" are gone.
  • The verbs are plain: "exists because", "are rejected", "keep working".
  • 429 is the standard HTTP status for a rate-limited request, so adding it is not invention. Which resource runs out, and how fast, the original does not say, and the rewrite does not guess. A writer who knows the system should name it.

Version 1.x of this rewrite added a retry loop, a scraper, a database connection pool exhausted "in seconds", and a Retry-After header. All are plausible and none was in the original. It also ended on "That complexity is cheaper than the outage it prevents", a closing line that repeats the paragraph as a saying.

A draft in the 2026 fragment style

Examples 1 and 2 start from the 2023 style: "testament to", "Moreover", "plays a crucial role". Community reports on Claude Opus 5 describe drafts like the one below. It has dropped the 2023 vocabulary and kept the negated contrast and the dash. The figures in it are made up for the example.

Before

The cache isn't slow — it's doing exactly what we told it to. That distinction is load-bearing. Every request hashes the full payload; in theory that's cheap, in practice it's 40% of p99. Here's the part worth stating plainly: we never needed the full hash. The key is the user ID and the route. Nothing else. So the fix isn't a faster hash function. It's a smaller key. Two fields, not two kilobytes. The numbers carry the argument: p99 drops from 310 ms to 190 ms. Small change. Big lever.

After

Hashing the full request payload (two kilobytes) for the cache key takes 40% of p99 latency. The cache only needs the user ID and the route to identify an entry, so the key can be built from those two fields. With the smaller key, p99 falls from 310 ms to 190 ms.

What changed, and why

  • The two negated contrasts are gone ("isn't slow — it's doing exactly what we told it to", "the fix isn't a faster hash function. It's a smaller key"). Nothing in the passage suggests the reader thought the cache was slow or wanted a faster hash, so the rewrite states what is true.
  • "Load-bearing", "carry the argument", and "big lever" each stood in for "this matters". The 40% figure already shows that it matters, so they are deleted without a replacement.
  • "Here's the part worth stating plainly:" is deleted and the thing it announced is stated.
  • The fragments are deleted. "Nothing else." and "Small change. Big lever." repeated the sentence before them. "Two fields, not two kilobytes" held one fact, the payload size, and the rewrite keeps it in a parenthesis.
  • "In theory that's cheap, in practice it's 40% of p99" becomes the measurement.
  • Every number in the rewrite was in the original. It is three sentences where the original had twelve.

A draft in the 2026 long-sentence style

This is the style the 2026 measurements describe: long sentences joined with "and", verbs turned into nouns, and no short statement anywhere (reference/research/2026-update.md §1). It has no "delve" and no fragments.

Before

The implementation of the new caching layer resulted in a significant reduction in response times and an improvement in overall system reliability, and the team's utilization of a write-through strategy ensured the consistency of data across services and reduced the occurrence of stale reads, and these changes have increasingly demonstrated the importance of careful architectural consideration in the optimization of performance.

After

The new caching layer cut response times and made the system more reliable. The team used a write-through strategy, which keeps data consistent across services and reduces stale reads.

What changed, and why

  • One 61-word sentence became two. The break falls where the subject changes from the result to how the team got it.
  • Nouns went back to verbs: "the implementation of... resulted in a reduction" became "cut", "utilization of" became "used", "ensured the consistency of" became "keeps consistent", "reduced the occurrence of" became "reduces".
  • The last clause is deleted. "Demonstrated the importance of careful architectural consideration in the optimization of performance" says that the work mattered and gives no fact.
  • "Significant" is deleted and nothing replaces it. The original gives no figure for the reduction, so the rewrite cannot supply one. The fix that would help most is the measurement, and only the writer has it.