‹ BackHN Continuity

Thread

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

388 points · 240 comments · zazuke

  1. bengold14 · · focus · HN ↗
    I see this everyday. The problem is code is the wrong abstraction for the work we do. LLMs have solved coding, but they haven't solved systems, collaboration or system maintenance.

    Edit: Since I seem to have touched a nerve - I&#x27;ve been working on a project to solve this: <a href="https:&#x2F;&#x2F;www.archme.io" rel="nofollow">https:&#x2F;&#x2F;www.archme.io if you want to know my thoughts on the right abstraction

    1. verdverm · · focus · HN ↗
      When you say &quot;solved coding,&quot; what does this mean, what does it look like?

      I have strong disagreement because it sounds like, by analogy or proxy, we have also &quot;solved writing&quot;

      1. KeplerBoy · · focus · HN ↗
        It solved coding as in it&#x27;s significantly less of a bottleneck than it was before.

        At least that&#x27;s how I experience it. In the before times each non-trivial code change had a real opportunity cost as it would easily consume two days until I could even estimate whether this is worth looking deeper into.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.