‹ BackHN Continuity

Thread

Coding is not solved

584 points · 544 comments · firstSpeaker

  1. askonomm · · focus · HN ↗
    What I've found is that AI allows lazy and incompetent developers to be more lazy and more incompetent. This then has the effect that product quality suffers more, faster. As a result of the sheer amount of code now being pushed out, code reviews, a thing that previously somewhat prevented lazy and incompetent developers from pushing out horrible code, is effectively dead in the water since no human can actually review such amounts of code realistically anymore. Some companies have adopted AI to review code, which, well ... you have AI make code, AI review code ... I hope you can see the stupidity here if you expect to see any deterministic results at all.

    I guess time will tell if the consumer will adapt to the lower quality of products, allowing companies to justify the existence of lazy and incompetent developers, or if the consumer will push back, forcing companies to increase the quality of their developers.

    Note: I use AI every day and it is entirely possible to create high quality software with it, so long as you are not lazy and incompetent.

    1. whatever1 · · focus · HN ↗
      Even if you are competent I cannot review your 5,000 lines of code you produce per day vs the 100 you were producing before the LLM apocalypse.
      1. bitwize · · focus · HN ↗
        That's okay. Reviewing the code will become the agents' job as well.

        A couple more step functions in model capability of the type we've seen in the past year, and there will pretty much be no reason for humans to be involved in the development process at all. All humans would need to do is communicate clearly what needs to be made and flag problems as they come up.

        1. xpct · · focus · HN ↗
          "A couple more step functions" is doing a lot of heavy lifting here
          1. pydry · · focus · HN ↗
            It's the AI bro's mantra.

            It didnt go wrong

            And if it did, it was because you werent using the latest model.

            And if you were, it was because you didnt have the appropriate guardrails.

            And if you did, it's because you didnt have AGENTS.MD.

            And if you did, it's because you didnt prompt it properly.

            And if you did, it you're still going to be redundant soon because I'm sure the next model released will fix whatever went wrong.

            1. mywittyname · · focus · HN ↗
              I've stopped calling out Claude mistakes on team meetings because this is so true.

              I mean, sure, I could have predicted in what ways an LLM would fuck up, but there's just so many ways I can't keep up.

              We just had a major production issue because someone's LLM wrote queries against dev databases. Which are very obviously dev databases because they are labelled with dev in the name, and in the table descriptions. AI reviewer didn't catch it, neither did the human reviewer for that matter.

              1. ysajang · · focus · HN ↗
                someone's LLM wrote queries against dev databases... AI reviewer didn't catch it, neither did the human reviewer
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.