I don’t think it’s that hard; it just takes effort. And the effort is well worth it.

It's not that hard if you put in the effort and practice.

But if you don't want to and still want to use an LLM, there are low-bar choices you can make (using a technical writing skill, using ASD-STE100 Simplified Technical English, choosing your audience, proofreading at the end with human eyes to make sure it makes sense and doesn't repeat itself uselessly).

I think it shows either a) low respect or consideration for your audience or yourself, or b) laziness.

Trust yourself to write even if it's bad. At least it's human.

I assure you it won't be as bad as this (answer to FAQ: "Will OpenLogi support Logitech Flow?")

> It's on the roadmap, at the far end: a cross-computer pointer and clipboard bridge is a very large feature. The half that lives in the protocol already ships. OpenLogi drives Easy-Switch host switching over HID++ (0x1814/0x1815), and paired mice follow the keyboard when it switches hosts. If the rest lands, it will be opt-in and local-network only.

A great example of why Claude's writing is terrible is the sentence "The half that lives in the protocol already ships". I cannot imagine any human writing this.

What is the point of spending so much effort if some people are still going to call it LLM slop?

Huh? Bad human writers don’t write like LLMs, at all.

There's good technical prose on the site? It's all just fluff marketing that adds nothing.

> writing good technical prose is hard and a separate skill.

Hard things are hard. They’re not easy. But they’re worth it.

Most worthwhile things are hard without a bit of practice.