Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

But the problem is the tight coupling of prompts to the models. The half-life of prompt value is short because the frequency of new models is high, how do you defend a moat that can half (or worse) any day a new model comes out?

You might get an 80% “good enough” prompt easily but then all the differentiation (moat) is in that 20% but that 20% is tied to the model idiosyncrasies, making the moat fragile and volatile.





I think the issue was they (the parent commenter) didn't properly convey and/or did not realize they were arguing for context. Data that is difficult to come by that can be used in a prompt is valuable. Being able to workaround something with clever wording (i.e. prompt) is not a moat.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: