Hacker News Reader

Comment by sandrello | Hacker News Reader

Based on my experience with these tools so far, this seems exactly the kind of subtle but extremely severe bug that sneaks in when you start piling up layers of AI generated patches to a codebase without caring too much about the code.

View on HN

"extremely severe" - aren't we laying it on a bit thick here? The whole impact seems to be that users who have telemetry turned off got this feature ~2 days later, when the bug was noticed.

a "feature" that every user has asked for - which is the equivalent of changing claude.md to agents.md - and the release isn't even smooth because the telemetry isn't wired up quite right.

for an organization that is being used as a model for new agentic software development practices.... and every software exec on earth is trying to reshape their organizations after - its a pretty stupid bug for a feature that should've been straightforward in the first place + took forever for them to get around to.

its just kind of emblamatic of the rough edges that exist EVEN FOR SIMPLE THINGS whenever human judgement is totally removed the equation.

ps: apparently thats not how you spell emblematic - but I'm actually glad to leave a little humanity around given the topic :D

Or it’s as simple as “hey, they don’t want telemetry? Cool, we’ll turn off all the extra phoning home” and their feature flag code uses the same paths as telemetry because it’s the same endpoint, etc.

Oops, easy mistake!

Except it’s not a new issue. This is just the feature that made it a conversation topic.

Good thing they don't apply the same standards to security sandboxes.

and the enshittification lives on

The issue is that this is the thing that got “noticed”. The problem is that your program behavior is now unpredictable. Anything can happen!

Yep, especially with long contexts (and moreso if the last thing you were working on in the same context involved telemetry too). AI sneaks in weird conditions like this and then does the entire "You're absolutely right" thing if you're paying enough attention to catch it.

I used to actively use Msty for local models because it just worked and had a lot of nice advanced features. A few months ago they released their beta version of a Claw-like UI and mentioned using a version of it to develop Msty itself. Well, that was around the time I stopped using Msty because every update started breaking things and two updates in a row included bugs which wiped all my configs, chats, and history.

It seems to be exactly the opposite, a "fully human error":

https://news.ycombinator.com/item?id=49815363

Nothing to do with AI patches at all, nor was it a bug. It was intentional human behavior, a temporary rollout setting, that seems to have made sense.

But I guess that doesn't fit the "narrative".

> It seems to be exactly the opposite, a "fully human error"

"LLMize the succeses, humanize the failures." is the PR strategy at play here. Anything goes well it's because AI did it, anything goes bad it's because a human didn't catch it.

Wow people are cynical here.

No matter what happens to be the truth, HNers have a cynical narrative to fit it.

People are just paying attention to what is happening the world.

No, people seem to be adopting simplistic narratives and then slotting the facts wherever they most conveniently fit into their narrative.

You say cynical but employees at these companies also lie just as much as their leaders. It's good to be skeptical of people that want to capture generational wealth while destroying the planet.

People aren't cynical enough here.

One thing I do know is that an Anthropic employee is definitely NOT going to blame this on the model they are using.

I don't understand what you are talking about. Vibecoding IS a human error.

Except that, and this I find slightly amusing, is a situation where they definitely don't want to publicly blame the ai model when there are mistakes.

Reply on news.ycombinator.com