This cracked me up:
“So for now we probably should use it only for tasks where facts are not important, such as writing letters of recommendation and formulating government policy.”
:-)
10 karma · joined October 2, 2018
“So for now we probably should use it only for tasks where facts are not important, such as writing letters of recommendation and formulating government policy.”
:-)
That said, I do like PARA so built this centered around it, with a few GTD and ZK additions:
This!! And your related explanation is so good!
Simple and superb root cause analysis!
Thanks for letting me know that’s not correct!
I don’t upgrade to the latest version when it comes out thinking it may not be stable enough yet. And then I remember about it when I’m about to start working or in the flow. I know, silly excuses!
I would’ve thought they would let devs handle it because if anything they’re more capable of these kinds of things (not counting myself ofc :-))
I really need to let go of these self-sabotage tendencies fast!!
But I definitely panicked too and still a worried if I carried something over to my home network.
I’m a developer and at least superficially aware of the issues. Can’t imagine what non techies go through when faced with such situations!!
Google did send me two Security alerts (one for each laptop) when I tried signing in yesterday with my old pwd. So they must have reset my password or something?
In any case, lesson learned: never connect to an unsecured Wi-Fi again! (I rarely do, but I was at this conference last week trying to demo Appomate AI, and was wanting it to be as snappy as possible. Bad decision!)
Exactly!
> Yes, after spending more time trying to decypher the LangChain docs than it would take to roll-my-own, everything I've done so far has involved rolling-my-own.
Looks like quite a few are doing the same, that is, rolling their own. Wonder if there needs to be a way to do it where it's standardized but still feels like rolling your own.
> I still think I might need to work with LangChain however: I'm afraid it's going to be what employers will be looking for.
Yeah workplaces are so different than working on your own projects. Been there! Might be you can get started that way, and slowly help people "see the light"!
And we're on the same page as to the time it takes!
As for the alternatives, I think there are 3 things to think about: 1. LLM call itself 2. Orchestration of calls & monitoring/input/output 3. Integrations with external services
For #1, if we were to limit the discussion to model providers with REST APIs (OpenAI, Anthropic, Google, Cohere, Groq, Together, ElevenLabs all have them), I think it would be much simpler to build a simple wrapper directly on top of fetch or equivalent APIs and even skip the SDKs.
For #2, don't think LangChain is a better solution than alternatives like state charts.
#3 is where LangChain might offer some value, but it's pretty thin.
I totally agree that it suffers from premature or even wrong abstractions. I guess it's to be expected because it hasn't had enough time to refine those yet -- it takes years! But the issue is that once it's out in production maintaining backward compatibility becomes top priority and hinders the refinement process.
Could it be that you're not able to relate to how whatever you're doing actually matters? If so, I'd say speaking to a few would-be users might help.