[rafram]

30 seconds or a minute? Look at the diff he links to: https://github.com/datasette/datasette-agent/commit/a75a8b72...

Every browser has an inspector that can show you which element is causing overflow. You walk through the tree, find the offender, and add min-width or overflow. Zero tokens, just like in the old days!

Now, granted, because the garbage LLM code he’s working with has CSS inside HTML inside JavaScript inside Python (I wish I were kidding), finding the styles in his codebase might’ve taken a minute. But even then!

[redox99]

Yeah looking at that diff it should be very quick. My point was mostly that it was a bad metric, not if was correct or not in this particular case. I'm sure everybody's had a bugfix that took days to debug and it was just a couple of lines to fix.

Or sometimes a fix is obvious, but because it requires changing the code of a dependency, it's actually quite tedious to implement.

[dekdrop]

I was thinking of this too. It did all that what not only for a single line that is a simple thing even for someone new to web coding. That's to say the process matters more.

[swyx]

> Zero tokens, just like in the old days!

because you zero rate your own human attention, which you should value

[rafram]

Alas, LLMs require more attention, not less.

[ocharles]

A small diff /= a small change! They are completely separate things. Quite often a small diff is hours of actual work. Even in this case _finding_ those lines could have taken work - we don't really know.

[rafram]

Did you actually look at the diff, though? That’s the kind of change you make 10 times a day while working on frontend. It is a tiny change.