I attempt to solve most agent problems by treating them as a dumb human.

In this case I would ask for smaller changes and justify every change. Have it look back upon these changes and have it ask itself are they truly justified or can it be simplified.

Seem like a solvable problem. Per origin cache control. But actually just load the data locally

You don’t need to. Llm will do it for you and include the security bug

Debian is slower so npm is more attractive

There was never the business value. But now remember this axios case and use it as ammo for the next issue. Just don’t abuse it

Agreed. I wonder if this silicon is designed for this benchmark and if not how useful is it with real code.

I would be surprised if this silicon area could not be better utilized for something else

No, branch predictors are really important and even small improvements in them are extremely valuable on real loads. Improving branch prediction is both a power and a performance optimization.

Why would the center two cols be used for such low probability symbols.

The braces being so far and tucked away make it really bad for c like languages

This seems like an insane waste to me. Especially the ones on the lower row. For me it is the strongest position.

Most people who use a keyboard aren’t using it for c like languages.

? JavaScript is c like and thr most popular in the world

Most people who use a keyboard aren't using any programming language

I dislike the middle columns so I think this is quite a cool idea.

Give me enough time to reverse entropy

There is a mathematical model where it does. In game theory it is called tit for tat

Not all corruption is crime, but prob ought to be put into the laws to become crimes