‹ BackHN Continuity

Thread

Pop!_OS bans AI-generated code from much of its codebase

116 points · 167 comments · bundie

  1. brink · · focus · HN ↗
    I also have found that AI has not lived up to many of its promises and have dialed back what AI gets control of. My projects were turning into unmaintainable messes. The people who say coding is solved aren't paying attention.
    1. lucianmarin · · focus · HN ↗
      Yes. I started two projects with AI from scratch. Both abandoned, complete mess. Projects without AI are so easy to manage, maintain, add/remove features, etc. I use AI as a search engine on my projects instead of Google. I ask what's wrong with my code and change or improve it myself based on my experience.
      1. fignews · · focus · HN ↗
        Have you considered that maybe this is a reflection of your skills rather than that of the LLM?
        1. sirsinsalot · · focus · HN ↗
          Have you considered it isn't?

          Save your "you're holding it wrong" if you're not going to suggest how to hold it.

          Cult speak escape hatches are intellectually lazy.

          1. fignews · · focus · HN ↗
            Sure, happy to provide you with an example of how to hold it (turns out Steve was right) =D

            <a href="https:&#x2F;&#x2F;github.com&#x2F;NousResearch&#x2F;hermes-agent" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;NousResearch&#x2F;hermes-agent is 99% (just a guess) LLM generated. 1140 closed pull requests this week. 1.5k closed issues. The github insights page for commits doesn&#x27;t load for me presumably because it can&#x27;t handle this scale of commits. But I estimate ~1K commits per day on average.

            There&#x27;s a blog entry <a href="https:&#x2F;&#x2F;nousresearch.com&#x2F;refactoring-hermes-with-1393-agents" rel="nofollow">https:&#x2F;&#x2F;nousresearch.com&#x2F;refactoring-hermes-with-1393-agents that details some work that was done by LLMs to refactor and improve the code.

            I guess they know how to hold it?

            1. chmod775 · · focus · HN ↗
              You&#x27;re using quantity metrics to answer a quality question.

              I had a look at the kind of issues that are reported at that project (there&#x27;s 15k of them, so I can at best assess a couple). It looks like a complete mess: A lot of concurrency and resource mismanagement issues and edge cases that in a better-managed project would have been avoided by construction. They will now will likely be solved by more defensive programming, driving overall complexity ever upwards.

              If you really want to check some quantity metrics to try to reason about code quality, look at whether &quot;fix&quot; PRs are overall LOC neutral or negative (not counting tests). In this project, almost every &quot;fix&quot; is an addition. Worse, almost every fix is more branching.

              If almost every PR is some sort of fix, and most of them add branching, and there&#x27;s thousands of them weekly... That leads to only one place and I want to be nowhere near it.

              1. nvme0n1p1 · · focus · HN ↗
                Agreed. As they say, quantity has a quality all of its own.

                Show me an AI that adds features by deleting code (<a href="https:&#x2F;&#x2F;www.folklore.org&#x2F;Negative_2000_Lines_Of_Code.html" rel="nofollow">https:&#x2F;&#x2F;www.folklore.org&#x2F;Negative_2000_Lines_Of_Code.html) and I&#x27;ll pay attention.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.