Hacker News new | past | comments | ask | show | jobs | submit
I think we're already limited by our own desires when it comes to coding.

The reason you can't one-shot something complicated is that you haven't generally considered all the important choices. You have to be asked for every choice, and complicated things have a lot of choices. But I think you can do something waterfall-esque, which used to be a big no-no in programming, if you just list out all the decisions meticulously.

I've had some success with doing that, just talking it over and thinking a lot about design decisions, making a document, and then letting it loose on the implementation. Inevitably, you find that there were contradictions or missing choices in the design, and you have to answer some questions.

So, not one-shotting, but it's my fault, not the AI's fault.

You can of course tell it to just fill in the gaps with whatever it thinks is reasonable, and then you'll have something potentially quite different from what you imagined.

The big improvement still coming down the pipe is that the models have better "taste" about filling in the things you didn't meticulously specify. A model from a year ago could make an amazing game, but you had to specify every detail precisely; now you can get similar quality results with a much more vague prompt.
That was the idea behind waterfall. You can look up how good that worked.