‹ BackHN Continuity

Thread

Writing Rust code that's fast by asking agents to make the code faster

114 points · 63 comments · mooreds

  1. hombre_fatal · · focus · HN ↗
    If it can be measured, then LLMs can optimize it.

    Once I had repo commands that could dump `sample` results and a cpu profiler/trace and then a benchmark tool that let me A/A + ABBA/BAAB-test the current modified git workspace against HEAD or any commit, the LLMs could just do their thing.

    And that's how my homemade terminal uses much less memory than ghostty/kitty/iterm yet has more throughput.

    AI is going to increasingly unmask people and companies who don't care about correct and performant software now that it's become so trivial to guarantee both. It used to at least be expensive and time-consuming and expertise-demanding to do those things.

    1. Capricorn2481 · · focus · HN ↗
      > If it can be measured, then LLMs can optimize it

      Then they can start attempting to optimize it. They can also spin round and round making the numbers worse because they don't actually know what to do.

      1. Conscat · · focus · HN ↗
        I had this experience at work trying to optimize a little high level Pytorch. It can't really get better than it already was, but LLMs were quite willing to pretend they will. The real solution is I need to open a PR for one of Pytorch's tracking issues.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.