4 ms·
Maybe I just need to get over it, but this post reeks of Claude-isms and it immediately makes me stop caring about what the post has to say. Obviously having a
by genshii 2mo ago
Maybe I just need to get over it, but this post reeks of Claude-isms and it immediately makes me stop caring about what the post has to say.
Obviously having an LLM write these kinds of things is the norm now, but what doesn't have to be the norm is the writing style. The way Claude (and other popular LLMs) write is so obnoxious and verbose. I think a simple pass of "make this more terse and to the point" would do wonders here.
- faldor20 2mo agoAs much as the content and tech behind it is really cool, and I appreciate Ryan's ideas it does seem like a shame to culminate so much work with a very "sloppy" finish
- ryansolid 2mo agoIt was human written, fed to AI, human adjusted, re-fed, and around again — for days, with dozens of reviewers in between. (GPT 5.6 Sol doing the AI half of the lifting, for what it's worth.) So "nobody even looked at it" is the one criticism I can rule out. Everybody looked at it. But you aren't wrong. The marketting heavy parts are where the tone shows. And honestly those are the parts I write worst. Exactly why I lean on AI there. When I ran before/after comparisons past reviewers, the polished versions kept winning. Maybe that's the norm creeping into how all of us write now. I notice it in my own sentences too. The words I choose. But given the choice between slightly synthetic and authentically clumsy, I tested both and shipped the one that read better.
- benrbray 2mo agoHey, I want to say that I love Solid as an alternative to react. I've been using it for hobby projects for 5+ years. I'm at least one example of someone who prefers authentically clumsy. Users like me will be less likely to give Solid a chance if they cannot see that there are real humans with a vision behind it.
- chrisjj 2mo ago> ... I tested both and shipped the one that read better And there we have it. "AI"s prime use case. Best instead of good enough.
- ricardobeat 2mo ago> And honestly :) The AI tone in the announcement is light enough to be barely noticeable, but it’s there. Note that posting AI-generated comments to HN is explicitly forbidden.
- ryansolid 2mo agoBefore: Anyone who has spoken to me knows I talk in run-on sentences. I never complete a thought without interrupting myself. And I write the way I talk. I used to heavily edit that out of my writing, but now AI uses the proper punctuation and fills in where I miss words. It's like what I hear in my head but better. Because it is grammatically sound. After: Anyone who's spoken to me knows I talk in run-on sentences. I never complete a thought without interrupting myself. And I write the way I talk. I used to spend whole editing passes beating that out of my drafts. Now AI handles the punctuation and fills in the words I skip. It's what I hear in my head, but grammatically sound. The result is almost always terser, more clear, and to the point. And usually all it takes is one more pass over to adjust anything I wouldn't say. In this case I kept the after verbatim just to illustrate my point.
- terabytest 2mo agoOut of curiosity, did you use AI for this reply too? It reads a bit like it.
- threatofrain 2mo agoRyan has given so much to this community... perhaps he gives too much.
- terabytest 2mo agoTo be clear I’m not making any statement or implication about Ryan’s work or his quality as a developer. As someone who knows nothing about Solid I’m trying to read the article and understand what the USP is and struggling. And remarking on the AI tells in the writing.
- owebmaster 2mo agoIs non-AI writing too much? I don't think his projects would have got as much attention if it was AI-written since the beginning.
- fn-mote 2mo agoAI knows how to spell “marketting”.
- wavemode 2mo agoPersonally I don't think that a release announcement needs to be "marketing heavy" in the first place. That's really the heart of the problem - in an effort to sound exciting, many parts of the article are just wasting the reader's time rather than simply explaining how things work clearly and directly.
- ryansolid 2mo agoNo release announcement has the time to explain how things work. I actually think in hindsight what Rich did by including a video in the Runes announcement worked well. I will have a livestream tomorrow.
- xg15 2mo agoWhy do you need several human/ai iteration rounds and dozens of reviewers for a blog post?
- ryansolid 2mo agoBecause it's important. You don't want to read my raw writing. Try to read my HackMD and you see what you'd get. It's always taken me a lot of work to release my medium and dev.to articles. Grammarly working hard, and multiple human editors. It scales with how many people I think will read it. A release announcement is important. It needs to be clear and it needs to convey the most information in a very short span. You don't have the privledge to meander in this sort of thing. And meandering is exactly what I'd do if left on my own.
- JacobParis 2mo agoTry writing the tweet announcement thread first - meander freely and use the character limit to help you truncate - split into one tweet per point, with one code snippet screenshot + quick explainer - either bullets like this or 2-3 sentences each Then your article becomes a slight expansion of the thread, where you can adjust language to make it flow better instead of starting with fluff and trying to carve it into something solid (I think of it like mobile-first design applied to writing) If the reason you don't like meandering or bad grammar is because you associate it with low quality/low effort writing, then the same can be said about standard LLM output. You may have gone through many iterations to land at this specific AI generated article, which stands up to your level of scrutiny over the content, but to anyone who doesn't scrutinize it just comes off like any other AI generated article.
- owebmaster 2mo ago> The marketting heavy parts are where the tone shows. And honestly those are the parts I write worst. Exactly why I lean on AI there. Everybody using AI to write slop do so because they think they can't write better but we all prefer a bad written article to the "correct" slop we are getting nowadays.
- chrisjj 2mo agoIs Claude really this bad, though? E.g. "The problem that never went away was async. Every framework, including ours, treated it as a condition that happened to it." Async treated as a condition? And a condition happens? And on grammar, the second it is ... the framework?? I rather suspect this is second-order output. Writings of a brain rotted by "AI". Shame, because enough of the message gets through the fog to tell me the whole message would be worth receiving. I wish the project every success.
- andrewingram 2mo agoThe article reads eerily like the Claude-authored drafts I did for some internal explanations of Relay’s design philosophy (it’s a GraphQL client I’ve been advocating for). I’m not one to make accusations of AI authorship, but it was a particularly striking impression with this one. I had to rewrite the drafts very heavily in my own voice in order for people to enjoy reading them —- not that I’m a great writer, but I am human and people tend to appreciate that.
- ryansolid 2mo agoHey want to see what AI generates when I ask it to talk about Solid 2.0. It's not that. It is: https://hackmd.io/@0u1u3zEAQAO0iYWVAStEvw/rJM9ws3Kbg https://hackmd.io/@0u1u3zEAQAO0iYWVAStEvw/rJM9ws3Kbg https://hackmd.io/@0u1u3zEAQAO0iYWVAStEvw/H1Q8XTMSbe https://hackmd.io/@0u1u3zEAQAO0iYWVAStEvw/H1Q8XTMSbe
- deleted 2mo ago[deleted]
- andrewingram 2mo agoI probably wasn’t clear with my experience. I was trying to get Claude to present my ideas, with a lot of steering and refinement, but it always seemed to be plagued by Claudisms. Even after getting rid of most, it took me rewriting all the prose to get something which people felt comfortable reading. The published post reminded my of where I got to after several rounds of review and cleanup.
- retropragma 2mo agoThis might be more palatable: https://gist.github.com/aleclarson/da55bca36103d582a9720dd4a4e2f87e https://gist.github.com/aleclarson/da55bca36103d582a9720dd4a...