‹ 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. bwfan123 · · focus · HN ↗
      At a startup I worked, there was an engineer whose code was incoherent and buggy. So, we were literally better off if that engineer did nothing because their net output was negative. Engineers like that become weaponized with LLMs, and negative numbers become larger negative numbers when scaled up.
      1. icedchai · · focus · HN ↗
        I've seen similar. They wasted weeks of senior engineering time, between reviews, meetings, and follow up in Slack, only to have the PR closed without merge. The offending individual was eventually moved to another project.
        1. taurath · · focus · HN ↗
          The bar has gotten so low that the idea that bad code doesn't get merged is the surprising part
          1. icedchai · · focus · HN ↗
            It probably would've been merged if it had a smaller blast radius. It had "fixed" (actually broken) many unrelated tests in the process of making a small update.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.