3 ms·
> The spec could simply be "take a query and return a paginated list of results ranked by personalized relevancy". The real problem is specifying what any of t
by skydhash 3y ago
> The spec could simply be "take a query and return a paginated list of results ranked by personalized relevancy".
The real problem is specifying what any of the quoted terms means (nouns and verbs). What is a query? What is a result? How many items in a page?... And then you recurse from whatever definitions and descriptions they gave you until what you have is terms from your favorite programming languages. Somewhere in the middle, you land into whitepapers and research materials. And sometimes the result is only good if you have PBs of data and lots of compute powers.
Having lots of code is not where you want to start unless you like to manage complexity from the get go and have clear understanding of the domain space.
- esafak 3y agoMost engineers are perfectly capable of understanding this specification without an explanation of each term. We can deal with ambiguity. So can ML models; that's what they're for. When we are not sure, we can ask for clarification or look it up. So can today's LLMs... I think natural language programming is a lot like dealing with a contractor.