alt Hacker News> prefer the coded format. Is is compact...
On the other hand "a folder that syncs files between devices and a server" is probably a lot more compact than the code behind Dropbox. I guess you can have both in parallel - prompts and code.
Replies
More compact, but also more ambiguous. I suspect an exact specification what Dropbox does in natural language will not be substantially more compact compared to the code.
You just cut out half the sentence and responded to one part. Your description is neither well defined nor us it unambiguous.
You can't just pick a singular word out of an argument and argue about that. The argument has a substance, and the substance is not "shorter is better".
What do you mean by "sync"? What happens with conflicts, does the most recent version always win? What is "recent" when clock skew, dst changes, or just flat out incorrect clocks exist? Do you want to track changes to be able to go back to previous versions? At what level of granularity?
"syncs" can mean so many different things
I’ll bet my entire net worth that you can’t get an LLM exactly recreate Dropbox from this mescription alone.
Let’s say that all of the ambiguities are automatically resolved in a reasonable way.
This is still not enough to let 2 different computers running two different LLMs to produce compatible code right? And no guarantee of compatibility as you refine it more etc. And if you get into the business of specifying the format/protocol, suddenly you have made it much less concise.
So as long as you run the prompt exactly once, it will work, but not necessarily the second time in a compatible way.