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.
bengold14 · · focus · HN ↗
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
verdverm · · focus · HN ↗
I have strong disagreement because it sounds like, by analogy or proxy, we have also "solved writing"
yetanotherjosh · · focus · HN ↗
Just to make this clear: if you can define a really good PRD and sophisticated technical specs, and a strong set of tests cases to pass, at the right level of architectural granularity, plus adversarial code review processes that triangulate and weed out most mistakes, SOTA agents can write the code autonomously, at or above the quality level of most human coding teams. I call that "solved" but only if you meet those context requirements. Which is still hard, not solved, at that layer.
Solving writing is not a good analogy IMO. Writing is for human consumption, and cannot be wrapped in objective requirements and verification processes. Certain forms of writing perhaps could be (can't think of one at the moment but I don't doubt some exist), and those forms might be good analogies for being "solvable" or "solved."
everforward · · focus · HN ↗
> Your concerns have moved up the stack to managing requirements, context, and verification processes.
This has always been the concern. "Add oauth to this app, there are no requirements beyond oauth working" has been an intern level task for ages. What makes software engineering hard is when the requirements start adding "well it has to use this oauth backend that isn't technically spec compliant, and the user is going to send some kind of random token you need to translate to oauth, and...". The problem isn't in writing code that will do the thing, it's figuring out exactly how that backend isn't oauth compliant and what chain of API calls I have to make to convert their random token into an oauth one, and etc.
Producing software that complies with a test suite isn't really novel. You've been able to outsource that forever. This falls apart in the same places outsourcing does; I'm sure India/Phillipines/etc/ is more than capable of iterating on code until it passes a test suite.