41–50 of 87 posts
Great feature. Although I’m starting to get annoyed by obvious signs of LLM writing like no X, no Y etc.
Does anything beat a free static site hosted with Cloudflare workers at this point, performance wise?
Earlier quoted context omitted.
They could just feed an llm a small corpus of past human authored posts from their site, and have the LLM rewrite it in a style matching style, and it would likely turn out pretty great.
I've tried this with my own blog posts from blog.jgc.org and the result was... not good. It basically wrote something that read like a parody.
Earlier quoted context omitted.
One of the recent AI tells other than em dash is the excessive usage of hyphenated words: > multi-tenant-safe cache keys > on a server-rendered app > byte-for-byte identical (classic) > gets a cache-speed response > cached-file-extensions list Honestly, this is terrible. I had to add a "use simple words only, don't hyphenate unnecessarily" warning to my Claude config. After a full day of work, having to read these Cl…
Fuck, I spent all these years developing a thoughtful writing style that leaned toward clarity for the reader, even if it meant extra work to achieve precision, or adding affordances like “excessive” hyphenation, and now I guess have to learn to write worse.
> This is the caching API we've always wanted Workers to have. Here's why it took us this long I was looking forward to the "why it took us this long" explanation but it wasn't explicitly spelled out. Any Cloudflare staff here able to expand on that? (The article does a good job of showing how many different smart design decisions went into this, but given caching is core to what a Cloudflare does I'm still a little…
Earlier quoted context omitted.
One of the recent AI tells other than em dash is the excessive usage of hyphenated words: > multi-tenant-safe cache keys > on a server-rendered app > byte-for-byte identical (classic) > gets a cache-speed response > cached-file-extensions list Honestly, this is terrible. I had to add a "use simple words only, don't hyphenate unnecessarily" warning to my Claude config. After a full day of work, having to read these Cl…
Fuck, I spent all these years developing a thoughtful writing style that leaned toward clarity for the reader, even if it meant extra work to achieve precision, or adding affordances like “excessive” hyphenation, and now I guess have to learn to write worse.
Even if you use em dashes and a few phrases that have become associated with AI writing, there’s still an unmistakeable sense of how much effort was put into the writing.
But I suppose there might be naive readers who don’t know how to spot this effort and would false positive on em dashes or supposed AI phrases.
Earlier quoted context omitted.
Not the original commenter; but, at least for me, the idea is that when it’s written by humans we know that effort and care were put into communicating the news. Otherwise they could post a link to the docs and we could ask my flavor of LLM to summerize. No need for extra filler content. That why it’s slop and it’s different.
I don’t have access to my flavor of LLM on the train nor the time or budget to have it do the research and summary for me Why are we all of a sudden pretending like pre-LLM era blogs were these pristinely well written pieces of art or even that effort and care was put into them? In most cases they were significantly less coherent and incomplete. Don’t get me started on the mess that was the communication of this part…
The LLM explained the core concept and features very well. But it was dull and boring to me, as I already have to read this writing style at work pretty much all day every day.
I just don’t understand why undermine your own announcements by delegating comms to the machine. It’s disrespectful to the reader.
Please please please write your own blogposts. I already read “but here’s the biggest unlock, and it’s the part that’s hardest to see” all day. I just don’t understand why undermine your own announcements by delegating comms to the machine. It’s disrespectful to the reader.