Thread

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

388 points · 240 comments · zazuke

bengold14 · 1790612793 · 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've been working on a project to solve this: <a href="https://www.archme.io" rel="nofollow">https://www.archme.io if you want to know my thoughts on the right abstraction
1. cmrdporcupine · 1790613500 · focus · HN ↗
  Even if they "solved" that, the problem is it's the LLM that "knows" it, not the team.
  Which is really the same problem with coding.
  The agentic model of it just taking over and doing everything is poisonous to effective long term team work.
  We're well past the point where it's about the quality of the work they produce. It's the way they integrate (or rather, don't) into human practices.
  1. bengold14 · 1790615815 · focus · HN ↗
    See my edit on the right abstraction - how do we get humans able to collaborate with agents effectively, where knowledge flows both ways, without needing a human to read 10k LOC, or even just lots of long LLM responses, to follow along

Unofficial Hacker News client; not affiliated with Y Combinator.