←back to thread

203 points dahlia | 6 comments | | HN request time: 0.737s | source | bottom
1. HL33tibCe7 ◴[] No.45153174[source]
Stopped reading after realising this is written by ChatGPT
replies(3): >>45153243 #>>45153278 #>>45154607 #
2. bfung ◴[] No.45153243[source]
Looked human-ish to me, what signs did you see?
replies(1): >>45155590 #
3. cazum ◴[] No.45153278[source]
What makes you think that and not that it's just an average auto-translate job from the author's native language (Korean)?
replies(1): >>45153502 #
4. urxvtcd ◴[] No.45153502[source]
I’ll go one step further: what makes you think it’s an average auto-translate job? I didn’t notice anything weird, felt like your average, slightly ranty HN post. I’m not a native speaker though.
5. akoboldfrying ◴[] No.45154607[source]
I found the content novel and helpful (applying a known but underappreciated technique (Parse, Don't Validate) to a common problem where I hadn't thought to use it before) and the tone very enjoyable. In fact, it's so idiomatically written that I can't even believe it's just a machine translation of something written in another language.

In short, a great article.

6. bobbiechen ◴[] No.45155590[source]
I thought the style was like ChatGPT in a "clever, casual, snarky" prompt flavor as well. I see it a lot on LinkedIn especially in sentence structures like these:

"Invalid data? The parser rejects it. Done."

"That validation logic that used to be 30% of my CLI code? Gone."

"Mutually exclusive groups? Sure. Context-dependent options? Why not."

For me this really piled on at the end of the blog post. But maybe it's just personal style too.