The fact that Gruber points to a "must-read" article about how the watermarking works, which, in turn, was very obviously entirely LLM-generated, says a lot about his lack of experience reading LLM output.
If Gruber can't tell a fully AI-generated article from a human-written one, perhaps he shouldn't care so much.
NB: I was told yesterday it's apparently a meme to call out Claude-generated output, but here I am, as I believe it's quite relevant to the topic at hand.
Yeah I've had all my personal project domains at Namecheap for a very long time but have been meaning to move over to CloudFlare. Guess I should get on that...
I really constantly have to fight the urge to NOT say/write something because it might be obvious or someone might have said it before.
Just say it.
I recently gave a talk about lessons learned in the past, and it felt really awkward, like, "who am I to tell people what to do?". A few days later, a student walked up to me and thanked me for it, because he adopted a practice I had suggested and thought it was useful. And I had troubles sleeping before the talk because I kept thinking about how plainly obvious it was going to be.
I started blogging again when I discovered that indeed, even if it's only me who finds this useful, it makes sense to write about it. As an exercise in writing, or in case there's at least ONE person on the internet who finds it useful.
> Two small fixes, in order. First, each cut endpoint is allowed to slide a tiny bit (up to 60ms) to land in the quietest spot nearby. If there’s a momentary lull in the audio just before or after the original cut point, slide there. The slide is bounded so it can’t cross into a neighboring word, otherwise you’d chew off real speech. Second, from that quiet spot, the endpoint snaps to the nearest moment when the waveform is exactly crossing zero.
Huh, I think the author might be deliberately ignoring how MCP works?
- "CLIs need to be published, managed, and installed" -- same for MCP servers which you have to define in your config, and they frequently use some kind of "npx mcp-whatever" call.
- "Where do you put the API tokens required to authenticate?" -- where does an MCP server put them? In your home folder? Some .env file? The keychain? Same like CLI tools.
- "Some tools support installing skills via npx skills, but that only works in Codex and Claude Code, not Claude Cowork or standard Claude" -- sure, but you also can't universally define MCP servers for all those tools. You have to go ahead and edit the config anyway.
- "Using a skill often requires loading the entire SKILL.md into the LLM’s context window, rather than just exposing the single tool signature it needs" -- yeah, but it's on-demand rather than exposing ALL MCP servers' tool signatures. Have you ever tried to use playwright MCP?
I just don't buy the "without any setup" argument.
Except that when its system prompt is full of instructions, caveats, design principles, gotchas, architecture notes, memories from the past, and personal preferences, at some point it's going to just ignore them outright. Heck, Claude Code won't even use critical instructions from a 100-line CLAUDE.md file sometimes. So you still have to be extremely vigilant about noncompliance.
My CLAUDE.md is deliberately very short, and only includes very specific rules like "never list yourself as a co-author or committer in git commits". Claude will very regularly ignore this rule, apologize every time I tell it to fix it, update its memories, etc. and then an hour later do the exact same thing again.
That is really a bit of an oversimplification IMO. Please check, for example, the Netflix tech blog and read about what has changed in the past 10 years or so when it comes to architecting video processing and video delivery systems. There's a tremendous amount of engineering work there which advances the entire industry. For instance, it's not trivial to add live events to a VoD infrastructure at that scale — it's not like you just add a few more nodes and buy faster encoders.
If Gruber can't tell a fully AI-generated article from a human-written one, perhaps he shouldn't care so much.
NB: I was told yesterday it's apparently a meme to call out Claude-generated output, but here I am, as I believe it's quite relevant to the topic at hand.