Hacker News Reader

> Taken to the extreme, a sufficiently broken down prompt is simply the code itself

it is not. But the artifacts generated through the steps will be code. The last prompt will have most of the code supplied to it as the context.

View on HN

No he is right, he is saying taken to the extreme. The point is the more and more specific you have to prompt, the more you are actually contributing to the result yourself and the less the model is

Yes but the build up isn't manual. You go patching prompts with responses until the final result. The last prompt will be almost the whole code complete, obviously.

Again, you are missing the "taken to the extreme".

What has happened to HN discourse recently?

I'm asking the same question. "taken to the extreme". What bullshit measurement is that?

Taking things to the extreme is rarely that useful in nuanced discussion though (it ignores that the optimal approach is rarely at the extremes).

A prompt is just a specification for an output. Code is just what we call a sufficiently detailed specification.

Reply on news.ycombinator.com