The problem is not AI code, but not knowing about system architecture or intent
Thread
Unofficial Hacker News client; not affiliated with Y Combinator.
The problem is not AI code, but not knowing about system architecture or intent
Unofficial Hacker News client; not affiliated with Y Combinator.
glouwbug · · focus · HN ↗
It boggles me we completely forgot that the world operated like this just 4 years ago
poisonborz · · focus · HN ↗
You can still write anything by doing it either small steps, or at once followed by a lot of refactors while skimming over code and asking tons of questions / making refinements via prompts, guidelines, test guardrails. A team can still reason and whitepaper about the same things. Devs who were previously shy to ask some specific details (to not seem dumb) can now confidently survey big codebases and get insights in whatever style they can swallow.
The bigger problem I see is that all this requires a lot of communication, and most importantly writing skills, something that disappears in thin air in the last decades.
AppleBananaPie · · focus · HN ↗
Folks break everything all the time and looking at their PRs and messages are clearly just having the AI respond to everything for them and actually have no idea what they're doing.
And then other people doing the same thing approve their work (presumably not reading or understanding any of it) because then the other person will do the same for theirs.
Hopefully my experience is an anomaly though :)