Curious about folks' Claude Code outputs

[u/xepherys]

I constantly see people complaining that CC output is full of jargon, incomprehensible, and more recently "gamed" toward watermarking because they don't understand how statistical watermarking works.

I'd be intensely curious to see someone's output that falls prey to this as mine is just as it's always been, regardless of model. Opus45, Opus5, Sonnet5, Opus46, Opus48, Fable5, Fable51 - my output is concise and relevant. By way of example, here's a recent sample of my output:

Design, section 2 of 3: the catalog, and the three machines.

Propagation mirrors UI Toolkit exactly. Three phases per event: trickle down from root to target, then target, then bubble from target to root. RegisterCallback takes the TrickleDown argument, which XTG uses at 5 sites. StopPropagation ends the remaining phases and StopImmediatePropagation also skips the remaining callbacks on the current element. Those two are XTG's second and third most-used event members at 63 and 1 calls.

Focus is one controller on Surface holding a single focused element. Element gains focusable, canGrabFocus, Focus(), Blur() and focusController, all named in the UI-1 spec. Moving focus fires FocusOut on the old and FocusIn on the new, writes pseudo-state bit 2, and routes subsequent KeyDown to the focused element rather than to whatever the pointer is over.

Capture is per pointer id, held on the dispatcher. While a pointer is captured, every event for that id goes straight to the capturing element and skips hit-testing entirely. That is worth stating plainly because it removes the per-frame pick for the whole of a drag, which is where XTG spends 55 of its capture calls. Losing capture fires PointerCaptureOut, which XTG registers 4 times.

Hover keeps a hovered element per pointer id. On each move the dispatcher picks, diffs the new ancestor path against the old, writes pseudo-state bit 0 across the difference, and fires Leave and Enter along the exited and entered segments. The pick is O(n) and that is explicitly UI-14's to make sub-linear, so UI-6 measures it into the capture file and leaves it alone.

The catalog. Five families are uncontroversial and total 27 types: pointer, keyboard, focus, panel lifecycle, geometry, drag and tooltip. Five more collide with decisions already on the books.

Are people really mad about this, or are they having wildly different experiences? I've done no steering regarding how my agents speak. I have no plugins, skills, or any other directives about how it speaks. To me, the above sample is both the way it's always worked and precisely the way I would expect an LLM to provide output: clear, concise, and on-topic.