Omni Topic - Tech

A new analysis of roughly 460,000 GitHub pull requests found a distinct vocabulary cluster resembling Claude's writing style jumped from 0.7% in early 2025 to nearly 39% by mid-2026. The study never looked at the actual code changes, only the words contributors used to describe them. Specific terms like 'load-bearing,' 'seam,' and 'byte-identical' turned out to be reliable markers of this shift. What Happened An independent study clustered roughly 460,000 GitHub pull requests purely by the vocabulary used in PR descriptions and commit messages, ignoring the underlying code entirely. It found that a specific writing-style cluster grew from just 0.7% of PRs in early 2025 to nearly 39% by mid-2026 — a shift large enough to reshape what a 'typical' PR description looks like across a huge, real-world sample. The Telltale Words The cluster is marked by recurring word choices: 'load-bearing,' 'plainly,' 'quietly,'...

A growing number of professionals are quietly tuning out documents that read like they came straight from an AI model. A recent essay describes the moment recognition kicks in — a design doc, a marketing deck, a requirements file — and how attention immediately drops. The pattern isn't about AI use itself, but about how obviously unedited the output is. What's Happening An essay circulating among developers and knowledge workers describes a specific kind of fatigue: the moment you spot low-effort AI-generated content in a work document, your focus collapses. Instead of trusting what's already written, you end up going back to the sender and asking them to explain it again — even though the answer is technically right there on the page. The examples given are concrete. A design document laced with phrasing characteristic of Claude. A 20-page marketing deck padded with statements that sound technical but carry no actual information. A requirements document so rambling ...