-20
"Coding" is Largely "Solved"
(raymyers.org)
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities !webdev@programming.dev
It's vaguely the same, though. We are abstracting technical language via natural language, but the details still have to be provided in some way. Leaving it to the AI to infer only works for very tiny things where ambiguity is low. For big things you have this ocean of slop because the AI still needs every detail specified else it will make shit decisions based on shit inferences.
I think a dev harness such as the one my company is trying to create is nothing more than trying to get the AI to make zero decisions and ask about even the slightest ambiguity — as it should.
So you wind up with an excruciatingly long detailed natural language spec that consumes boatloads of tokens and is impossible for a human to read through only to produce the exact same thing translated into code.
From that perspective, it's just an abstraction layer. A very sloppy one.
I agree. I recently chatted with an ex-dev manager who tasked two of his devs with coding a new feature entirely through AI. They succeeded, but lamented that they had pages and pages of prompt to get it right. "You guys have rediscovered the concept of a 'design doc'," he told them.