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!

I looked at the screenshot and for the rest of the article wondered if it would be as simple as `overflow-x: hidden`.

And to my surprise it was.

This would’ve take a frontend dev 10 seconds to deduce and another 10 seconds to confirm.

I mean - that looks like a pretty easy CSS fix to play around with in developer tools, and I'm not even a frontend person. Maybe a few minutes max?

5 minutes if you know CSS. And if you don’t, about the time for you to ask someone that knows CSS. In the worst case, the amount of hours to learn CSS.

So if you’re doing web pages, learn CSS.

Generally, if you’re doing something that directly involves X, learn how X works.

ADDENDUM

In most jobs, you’re going to be involved in only a few distinct technologies, learn those well and life is going to be easier. And most are transferable to the next job.