I sort of agree, but I also think the advice here is circular. To look at the style suggestions produced by an LLM and decide that you agree with some of them in spirit, but want to put it in your own words, you already need how to know how to write well.
In other words, you need to read a style manual or two, and you need to read and have opinions about other people's work. You must have taste. Otherwise, you can't really distinguish between good and bad advice. You'll anchor to the suggestions made by the LLM and it will turn your writing into LLMese. I guess that works - it sure gets clicks on HN - but it won't be your voice anymore.
There's still value in getting a second pair of eyes on what you write. But here's another cool trick that gives you a similar benefit: just let it stew. Go for a walk, grab a lunch. Re-read what you wrote. You'll be surprised.
I wrote the article. I am not interested in "style suggestions" from the LLM; I'm interested in things I can verify for myself. Is this word or construction overused in the piece? Is there a pointless throat-clearing like "it's important to note that" crudding up this paragraph? Am I overusing vacuous nouns like "issue" ("the big issue is that") or "factor" ("the next factor to consider is")? Do I have my verbs buried in nouns, like "distortion" where I should just use "distort"?
I don't care whether the LLM likes these constructions or not. I don't like them. I usually don't want to keep them in my work. It's my call what to change; I just want issues flagged.
Your prompts would be different. Or, they would if you decided that having an LLM merely point things out about your own writing wasn't itself a form of contamination. You do you!
I wrote this article in about 45 minutes and didn't workshop it with anybody else, so I'm not surprised it's gone over people's heads; it was just something I was talking about on Twitter that I wanted to get down on a page. But it's pretty obvious that a lot of people here have missed the point.
I think your take has more application than writing. I also suspect that Jev-like use cases for LLMs will begin to overtake the generate-all-the-things paradigm in programming, contracts/legal, music.
People are beginning to wisen to how to more skillfully deploy generative models.
in_absentia · · focus · HN ↗
In other words, you need to read a style manual or two, and you need to read and have opinions about other people's work. You must have taste. Otherwise, you can't really distinguish between good and bad advice. You'll anchor to the suggestions made by the LLM and it will turn your writing into LLMese. I guess that works - it sure gets clicks on HN - but it won't be your voice anymore.
There's still value in getting a second pair of eyes on what you write. But here's another cool trick that gives you a similar benefit: just let it stew. Go for a walk, grab a lunch. Re-read what you wrote. You'll be surprised.
tptacek · · focus · HN ↗
I don't care whether the LLM likes these constructions or not. I don't like them. I usually don't want to keep them in my work. It's my call what to change; I just want issues flagged.
Your prompts would be different. Or, they would if you decided that having an LLM merely point things out about your own writing wasn't itself a form of contamination. You do you!
I wrote this article in about 45 minutes and didn't workshop it with anybody else, so I'm not surprised it's gone over people's heads; it was just something I was talking about on Twitter that I wanted to get down on a page. But it's pretty obvious that a lot of people here have missed the point.
politician · · focus · HN ↗
People are beginning to wisen to how to more skillfully deploy generative models.