> Why supply underspecified requirements in the first place?

Minimizes effort, is the obvious answer.

Poor trade off, the model is then designing a massive chunk of your solution instead of you. With a good spec, bits of typo’d pseudocode, and slightly more effort than a couple of sentences they can actually produce passable software.

I think the reason claude has so much mindshare is exactly because it’s more useful to non-developers who wouldn’t know how to describe what an api call executes to his grandmother.

For those who can, I can’t find much of a difference between them. Codex has the slight edge, but that’s all just “feels” to me.

	▲	ben_w 4 minutes ago \| parent [-]
		You call it a poor trade off, but: > I think the reason claude has so much mindshare is exactly because it’s more useful to non-developers who wouldn’t know how to describe what an api call executes to his grandmother. This is exactly the benefit for most people. Most people don't want to code the app, they just want the app. Even people like us who do like coding, we can only think of all of these things within a domain that we already know; somebody who writes shaders for games isn't likely to know or care much about the ins and outs of database development or how healthcare privacy law and KYC interact with zero-knowledge proofs. (Of course, if the AI knows about these things and then completely fails to make use of that knowlege, that's still a fail).