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.
Hyperbole = strong opinions? If you're stating your 'strong opinions' as fact, then you deserve the push back. If you're stating your strong opinions as strong opinions, then fair game.
If I want to say that iOS is useless for developing Bluetooth 5 features then this is true for all practical purposes and doesn’t deserve elaboration in my text, even if Apple’s API technically exposes one or two tiny pieces.
You say this but fact and opinion are very similar and not at all easy to distinguish.
For instance, if I said the grass is green vs if I said the grass looks nice vs if I said the grass is doing well and looks how it should vs if I said in my opinion the grass is healthier than its ever been.
If a model complains about hyperbole, that doesn’t mean the text is hyperbole, and this can be because of the context of the text or because of the hedging the models are wont to do
thombles · · focus · HN ↗
ralphington · · focus · HN ↗
matheusmoreira · · focus · HN ↗
Is there anybody on this site who isn't?
maleldil · · focus · HN ↗
thombles · · focus · HN ↗
ferngodfather · · focus · HN ↗
For instance, if I said the grass is green vs if I said the grass looks nice vs if I said the grass is doing well and looks how it should vs if I said in my opinion the grass is healthier than its ever been.
dan-robertson · · focus · HN ↗