51–60 of 87 posts
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.
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…
Aren't you gonna let the LLM develop for you anyway? Why bother writing and reading a post at all?
> pretending like pre-LLM era blogs were these pristinely well written pieces of art
The point is the effort and care that the writer puts which differentiates it from automatically generated text. That matters because a human can sympathize and that leads to better understanding and greater connection. That's why a post is written.
> Don’t get me started on the mess that was the communication of this particular company or one of their competitors like AWS.
And we criticize those as well. Nothing's changed. Yesterday's bad content is today's slop (plus a mind boggling amount of investment, corruption and environmental side effects).
Great feature. Although I’m starting to get annoyed by obvious signs of LLM writing like no X, no Y etc.
Great feature. Although I’m starting to get annoyed by obvious signs of LLM writing like no X, no Y etc.
At least for me I don't really read these posts/docs, I just give the link to claude and it'll implement it regardless of wording
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.
At least for me I don't really read these posts/docs, I just give the link to claude and it'll implement it regardless of wording
Thanks CF.
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.
There has to be some sort of "/humanize-text" skill they can pass the output to before publishing.
I found it funny to just read through.
- You still get billed per request, whether the request hits cache or not (but don't get billed for CPU time)
- You now get billed for static asset requests! This makes no sense to me. "One thing to watch: when caching is enabled, requests that are normally free — static asset requests and worker-to-worker invocations through service bindings or ctx.exports — are billed at the standard request rate, because each one now consults the cache in front of your Worker." Yeah that sounds like a bug that just happens to generate them more money.
- The cache key automatically has the worker deployment version, so even gradual deployments populate their own cache which is nice
- It seems like you can set a totally custom cache key? But that was previously Enterprise only, can't see if that's still the case here.
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.
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…
I have an over-hyphenated writing-style as well. Probably my Germanness.