Thread

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

388 points · 240 comments · zazuke

glouwbug · 1790613143 · focus · HN ↗
When you write something you constantly remodel your understanding through refactors and rewrites until you internalize it. By internalizing it you gain the capacity to reason about it (during critical downtime) and communicate it. An entire team that can communicate can solve problems together, from one guy's vision to products white boarding to engineering's infrastructure to UX and UI's artistry.
It boggles me we completely forgot that the world operated like this just 4 years ago
1. desmondl · 1790616437 · focus · HN ↗
  > When you write something you constantly remodel your understanding through refactors and rewrites until you internalize it.
  Unfortunately I learned that not everybody thinks this way. Some orgs do imperfectly fine without good engineering discipline, and that has been the case before AI... AI has only made it easier to give the appearance of good engineering, which is exactly the pre-AI goal of many orgs

Unofficial Hacker News client; not affiliated with Y Combinator.