3 ms·
I think you’re still anthropomorphizing LLMs too much by saying the problem is a lack of curiosity. It’s an engineering problem: you haven’t figured out the cor
by agentcoops 3y ago
I think you’re still anthropomorphizing LLMs too much by saying the problem is a lack of curiosity. It’s an engineering problem: you haven’t figured out the correct “context” from which business requirements would follow. (And why Microsoft is so incredibly well positioned for the future)
- Swizec 3y agoCuriosity is how you build that context.
- agentcoops 3y agoI'm sure in your career you've seen countless attempts by 1000+ employee firms to spinup an ops team that must construct a giant spreadsheet of product priorities between customers, PMs and engineering teams -- versus having all of Salesforce, Slack, emails, meeting transcripts, user support messages, vectorised and fed into an LLM that any employee can converse with. The latter is not a trivial problem by any means and many, many implementation details, but I'm sure it's such an exciting time to be at Microsoft. Stratechery had a fantastic article about this. If I had to make a bet, I suspect Google and Meta will royally lose this generation: Apple will dominate personal access to LLMs, Microsoft will dominate business access to LLMs -- and honestly Palantir for the first time terrifies me. The current generation of LLMs are not about automation as such, but helping individuals accomplish self-directed goals (as possible in language and code).