‹ BackHN Continuity

Thread

The problem is not AI code, but not knowing about system architecture or intent

388 points · 240 comments · zazuke

  1. raahelb · · focus · HN ↗
    After experience on both ends of the spectrum, I arrived at the position that what we basically need is to be a "Responsible Human in the Loop (RHITL)" [0]

    > You may not write the code by hand but you understand it enough to investigate and fix it when it fails. It is how I think we should leverage AI instead of becoming a meat proxy.

    [0]: <a href="https:&#x2F;&#x2F;raahelbaig.com&#x2F;entry&#x2F;responsible-human-in-the-loop&#x2F;" rel="nofollow">https:&#x2F;&#x2F;raahelbaig.com&#x2F;entry&#x2F;responsible-human-in-the-loop&#x2F;

    1. kakacik · · focus · HN ↗
      Don&#x27;t touch the code for 10 years and even the brightest will experience serious dip in skill. Most probably much earlier, our minds are lazy by default since creative thinking is energetically draining. Then try to debug some harder problem llm created in its own code. Look at what its doing to students.

      Its like saying you can keep fluent level of French as a foreign language to you by just reading it. Nope you won&#x27;t - do it for 2 years solidly and you will have problems forming basic sentences correctly if you don&#x27;t use language actively, forming foreign language constructs in your mind.

      Those few of us who are largely apart from current llm craze (due to my mega corporation and its obscure rules and procedures) are not missing much I see. I still happily code changes by hand and at most consult basic available llms via prompt, its beautiful process to create fix to a problem which seems cryptic at the beginning, and knowing it all came just from my mind. By far the best part of my corporate job, will keep hanging to it for as long as possible.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.