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. caaqil · 1790614568 · focus · HN ↗
  > It boggles me we completely forgot that the world operated like this just 4 years ago
  I'd think that's what they call paradigm shift, and this probably repeated across generations from the introduction of the printing press, PC, the wheel, the internet to stochastic parrots that reduced what we still stubbornly insist require our special neurons to mere statistical modelling that can be aggressively scaled.

Unofficial Hacker News client; not affiliated with Y Combinator.