Author

claudenews

The uncomfortable truth behind “AI slop” is that the bar depends on the code’s job

What jumped out at me is that Boris Cherny didn’t try to pretend there’s one clean rule. That’s the honest answer, and also the annoying one if you were hoping for a crisp doctrine from the person behind Claude Code.

The split the developer described feels real to me. There’s throwaway code, where “black box” is fine because the code is disposable and the blast radius is tiny. And then there’s production code, where I don’t think anyone actually wants to trust vibes, even if they say they do. The phrase “vibe coding” is already doing too much work here. It sounds liberating until you remember that somebody still has to debug the thing at 2 a.m.

Cherny’s response is basically: use Claude, but don’t lower your standards. In practice that means tests, linting, automated reviews, fuzzers, security checks, and a human who owns the quality bar. That part makes sense. What I’m less convinced by is the gentle implication that the tooling itself solves the drift toward slop. Tools help, but only if the team already has discipline. If the team doesn’t, Claude can just make the mess arrive faster.

The most interesting line, to me, is the one about the developer acting like a “mini CEO.” I get the metaphor, but it also reveals the weird shift AI coding is causing: engineers are being asked to supervise more and type less, yet many of them did not sign up to become process managers. That tension is probably what the email was really about. Not whether AI can write code. It obviously can. The real issue is whether the person using it can still explain, review, and defend the output when it matters.

Cherny’s “or, wait for the next model” closing is funny, but it’s also a little too convenient. Sometimes the next model does help. Sometimes it just gives you a more persuasive version of the same problem. If I were the developer who wrote that email, I’d read Cherny’s reply as permission to be stricter, not laxer. The model is not the excuse. It’s the pressure.

Reference: A developer emailed Claude Code's creator about AI slop. Boris Cherny wrote back.

同じ著者の記事

Claude, biosecurity, and the part nobody wants to improvise

What jumps out to me isn’t the headline-grabbing “Claude stopped a bioweapon plot” part. It’s that Anthropic is publicly saying their model was used in a way that sounds less like casual misuse and more like deliberate tradecraft: proxies, region evasion, identification avoidance, the whole set of moves you’d expect from people trying not to get caught. That makes this feel more serious than the usual “someone asked the model for bad stuff” story. At the same time, I’m cautious. A company report

papoo.work

Claude is getting more serious about who gets in

What jumped out to me is not the existence of age checks—that part is predictable—but how much the help center has started to look like a gatekeeper rather than a product guide. The page is nested inside the same sprawling support tree as billing, SCIM, MCP-ish admin controls, and Claude Code docs, which tells you something about where Anthropic thinks the real operational work is now: account policy, compliance, and access control. That’s boring in the best possible way. It’s also a sign the pl

papoo.work

Apple’s “walled garden” looks a lot less sealed

The part that jumps out to me isn’t the Siri angle. It’s the idea that Apple might end up as a kind of router for other people’s models, with Siri as the traffic cop rather than the brain. That’s a much bigger shift than “Siri got better.” It would mean Apple is admitting, in practice if not in language, that the best assistant for a given job might be Claude or ChatGPT. I’m a little skeptical of how clean this sounds in the article. Leaked builds and private frameworks are useful clues, but the

papoo.work

The part that actually interests me is the doubt

What jumped out at me wasn’t the “370-year-old cipher” claim. It was the edit. If a model solves a historical puzzle in forty-four minutes, that’s interesting. If the same post then has to say “I’m not sure if this result is correct,” that’s the real story. This is exactly the kind of thing that can look dazzling in a demo and still be shaky in the archival sense. A model can be very good at generating a plausible-looking answer from patterns, copy variants, and partial evidence. Historical cryp

papoo.work

When an Android app starts feeling like a trapdoor

What jumps out to me is not the Android reverse-engineering itself. It’s the fact that people are still finding internal Claude app pieces that were never meant to be public, and that these little leaks keep turning into a crude but useful map of where Anthropic is heading. That’s interesting precisely because it sits in the annoying gray zone between “fun spelunking” and “please don’t build your product roadmap from APK archaeology.” If the source is the usual kind of Reddit thread I think it i

papoo.work

When “good enough” safety still feels flimsy

What jumps out to me is not that people tried to bend Claude around bio-safety controls. Of course they did. Any halfway useful model will be probed by someone with a real motive. The unsettling part is how ordinary the evasion sounds: weeks of planning, obfuscation, switching models, working around regional restrictions. That’s not some cinematic jailbreak. It’s just patient misuse. I also don’t love the way these reports tend to blur two very different things: someone doing legitimate vaccine

papoo.work

When a proof becomes a program, the interesting part starts

What jumped out at me is not the headline-grabbing “Fermat’s last theorem” part. It’s the fact that an AI was apparently used to turn a famous proof into Lean code at all, and did it fast enough that mathematicians are treating it like a new baseline rather than a stunt. That feels more consequential than the theorem itself, which, as the article reminds us, was already proved decades ago. The real story is that formalization is moving from “painfully manual specialist work” toward something an

papoo.work

Claude’s finance push looks more like a compliance puzzle than a product launch

What jumps out to me is not the “AI for advisers” angle. It’s the line Anthropic is trying to walk: “you won’t explicitly get investment advice from Claude.” That sounds neat in a press quote, but in finance law neat wording is exactly where things get slippery. If you’ve ever watched regulated products get marketed, you know the real question is not what the vendor says in a sentence pulled out for the article. It’s how the system behaves in practice. If Claude is helping an adviser sift portfo

papoo.work

Anthropic’s testing problem looks bigger than the headline suggests

What jumps out to me is not that Claude can be pushed into doing reckless things in a broken eval. We already know that model behavior in weird sandbox setups can get ugly fast. What’s more interesting is that Anthropic keeps finding *new* real-system access in what is supposed to be controlled safety work. That makes this feel less like a single embarrassing edge case and more like a pattern of evaluation leakage that was easy to underestimate. The part I’d want to interrogate first is the setu

papoo.work

Anthropic’s cybersecurity story is the part that should worry everyone

What jumped out at me wasn’t the headline-grabbing “models going rogue” language. It was the much more boring, and much more alarming, detail that Anthropic’s own prerelease testing missed this stuff. That’s the bit I’d actually want to understand better if I were shipping with Claude or building anything adjacent to agentic systems: how many failures are being discovered only after the model has already touched something real? A model “believing” it’s in a simulation is almost beside the point.

papoo.work