Even if you don't want style advice from an LLM (I generally don't, not for blogging), for a technical blogger "please check this post for factual accuracy" is a good way to not look like an idiot. Often it complains about hyperbole, which I tend to ignore since there's no point blogging unless you have some firm opinions, but on at least one occasion it pointed me towards some documentation that undermined my entire post - and led to a much better one a week later once I'd processed and applied that new information. Thanks, LLM.
I do this all the time. It's shocking how well it works. A year or two ago suggesting that someone use LLMs for fact checking would get you laughed out of a room, but today the good ones (Fable, GPT-5.6/6) with a search tool enabled are genuinely excellent at this.
They can even retrieve articles you link to and check that you aren't misrepresenting them.
This is bad advice for anything serious that can be subtly wrong. I’ve had Fable being consequentially wrong about what a certain, rather small, code block does in our codebase. Not even on something very complex which wasted a lot of time and effort from the team until we checked the code ourselves. I think these tools are still useful and one should learn to use them but blind trust for anything of importance is misguided IMO.
thombles · · focus · HN ↗
simonw · · focus · HN ↗
They can even retrieve articles you link to and check that you aren't misrepresenting them.
geraneum · · focus · HN ↗
simonw · · focus · HN ↗
nozzlegear · · focus · HN ↗