Did I even tried to pretend the article wasn't generated with Claude's help?
I even shared the initial prompt in some comment in this thread. I don't understand what is the matter with also using AI help with generating articles. I still reviewed the article and put all the ideas I wanted to discuss in that article. I don't see why people are often complaining about this. The article content is much more important than how it was generated.
I hear your frustration and it, er, prompted me to write some thoughts about the situation.
The community is trending strongly against wanting to read generated writing. It's unclear how it will shake out in the long run, but for the near term, this preference is clear*. We can debate the reasons or what the correct position is, but it doesn't much matter when there's such a strong community verdict.
We don't have a rule against genai in articles the way we do about text appearing on HN itself (https://news.ycombinator.com/newsguidelines.html#generated) but the pushback is strong enough that it's in authors' interest to write their articles themselves. Even seemingly less invasive tools like grammar checkers and translators leave strong LLM imprints on text these days.
There is an emerging class distinction in the culture: generated writing, or writing that sounds like it, gets stigmatized and relegated to a lower-status bucket in readers' minds. The converse is also true: writing that isn't generated, and doesn't sound like it, gets boosted into a high-status bucket. It's easy enough to turn this to one's advantage: simply write your own writing.
There are even signs that mistakes (e.g. in grammar or spelling) which would formerly have counted against an author and lowered their status, are turning into markers of authenticity. This is something we point out to non-native English speakers who post to HN: don't worry about your English, just write in your own voice, because that is the high-order bit now. (https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...)
I think your prompt was great, btw (https://news.ycombinator.com/item?id=49544844) and something most readers, including myself, would prefer to the generated output. Kudos for sharing it! We often hear readers saying they'd "rather see the prompt", but yours may be the first case I've seen of an author actually posting it.
There’s “how to be a good parent” advice and there’s also “oh boy how do we manage mealtimes and laundry and the school run” type advice. Someone with lots of kids is going to have great insights into the latter at very least.
I am the father, and I have a ton of involvement in the day-to-day work of running the house. This brings me and my wife a lot of satisfaction and it undoubtedly wouldn’t be possible if I was still commuting to work in Silicon Valley.
I’m basing this on the vibe from a chart someone showed me when I was in the hospital 8 years ago after my son was born. The point is the chances increase exponentially. Found the list now:
Age 20: About 1 in 500 (0.2%) Age 30: About 1 in 270 (0.37%) Age 35: About 1 in 80 (1.25%) Age 40: About 1 in 60 (1.66%) Age 45: About 1 in 20 (5.0%)
Which actually kinda refutes me because 1 in 500 is still a lot.
According to your logic, front end apps thus have three rendering engines: the server (rendering json), the browser, the JavaScript framework. Count the rendering engines like you want, the point still stands: server rendered apps are architecturally simpler.
There is no one size fits all solution. Frontend-heavy projects have their place, server-rendered ones too.
reply