You can cure Google's AI (but not bad results) with &udm=14

https://google.com/search?q=parkas&udm=14

A more easy reproduction: disable JS.

To bypass: `.transition_wrap { display: none }`

In their defense, I think that's the right move. There isn't an analogue for that page anymore, so it redirects to the new style guide's landing.

I think it's rather cool that they've redirects still going for (quick Archive check) 11-year defunct URLs.

Wall chicken is obliquely referenced in the article

Yeah, I didn't link the first archive as the Soundcloud playlist fully doesn't load. This one doesn't play, but at least the names are searchable.

That is not the source. In their housecleaning they removed graphics and anchors from the interview, so I'm providing the original.

ah, weird

Context from the prior year: https://pitchfork.com/news/69473-korg-announces-new-synthesi...

We need to take a page from baseball and examine Hacks Above Replacement

Originally from 2009: https://web.archive.org/web/20201101013903/http://legacy.han...

Previously: https://news.ycombinator.com/from?site=hanno-rein.de and https://news.ycombinator.com/item?id=39316193

This also reminds me of https://news.ycombinator.com/item?id=30024165

I'm a quite senior frontend using React and even I see Sonnet 4.5 struggle with basic things. Today it wrote my Zod validation incorrectly, mixing up versions, then just decided it wasn't working and attempted to replace the entire thing with a different library.

There’s little reason to use sonnet anymore. Haiku for summaries, opus for anything else. Sonnet isn’t a good model by today’s standards.

I have been chastened in the opposite direction by others. I've also subjectively really disliked Opus's speed and I've seen Opus do really silly things too. But I'll try out using it as a daily driver and see if I like it more.

Why do we all of a sudden hold these agents to some unrealistic high bar? Engineers write bugs all the time and write incorrect validations. But we iterate. We read the stacktrace in Sentry and realise what the hell I was thinking when I wrote that, and we fix things. If you're going to benefit from these agents, you'd need to be a bit more patient and point them correctly to your codebase.

My rule of thumb is that if you can clearly describe exactly what you want to another engineer, then you can instruct the agent to do it too.

> Engineers write bugs all the time

Why do we hold calculators to such high bars? Humans make calculation mistakes all the time.

Why do we hold banking software to such high bars? People forget where they put their change all the time.

Etc etc.

I don't hold calculators to high bars. They think 0.1 + 0.2 = 0.30000000000000004:

https://qntm.org/notpointthree

Some of them. The good ones don't.

my unrealistic bar lies somewhere above "pick a new library" bug resolution