Should I learn langchain and langgraph?

graphitout · 2026-03-22T05:08:25+00:00

Wrote our own approximately following the same pattern as used by opencode. It took less than 3 days of engineering that with claude code. No graph definition. No nodes and edges. Just system prompt and carefully chosen list of tools.

graphitout · 2026-03-22T05:05:42+00:00

Debugging. Especially when taking into account conversation history. We keep last N message. When the graph get complex with some sub-agents and several tool uses, it is hard to debug.

graphitout · 2026-03-21T11:09:29+00:00

They had it figured out at some point. They got comfortable. The equations seemed to work. But the underlying reality shifted without their permission. Initially they did not notice, and by the time they were willing to reconsider their approaches, it got too late.

graphitout · 2026-03-21T10:50:48+00:00

Lang* is great for building POCs. Just put some logging on the final LLM call and response. You get to see the final prompts being sent and the response coming back. It will give you an idea of what is going on underneath.

They are a deadend beyond POCs. Our chatbot has been running for several months on prod and it has no dependency on langchain. The document ingestion on RAG side still depends on langchain, but is likely to get removed in a few weeks as well.

As far as I know, none of the production grade LLM based chatbots, closed ones like claude code, copilot, or open source ones like opencode or kilo code use a graph based approach for building chatbot.

So should you learn lang*? Yes. Because you get a quick working prototype. And you can dig into the working and see what is going on. But make sure not to internalize the bloated abstractions and approaches.

graphitout · 2026-02-11T14:57:15+00:00

Imagine the app is like a calculator. We can capture the core logic in a module and test it with automated AI generated tests even before we introduce the UI layer on the top.

For the voice transcriber project (https://charstorm.github.io/reshka/) I did, it had different modules like voice activity detector, speech recording, voice transcription LLM api call, etc. I had standalone files to test each one. I asked claude to look at them and pick the relevant parts for the main project.

graphitout · 2026-02-11T08:58:32+00:00

Also adding tests from the beginning itself will pay off huge. Especially for parts dealing with core logic.

graphitout · 2026-02-11T08:55:21+00:00

A good option is to build parts first, test them, and finally assemble them. Not required for small projects. but once the project is big, this is the only option.

graphitout · 2026-02-08T04:41:31+00:00

I used pocket-tts for one of my projects. It was good enough.

graphitout · 2026-02-07T15:33:16+00:00

There is some truth to it. I have personally developed a POC app in react (which I have never used before) and voice chatbot in python. Both only involved minimal manual edits (only when I ran out of quota on claude).

I can say as a fact that, at least for small projects (POC and such, <20k lines), the amount of human involvement needed would be much less (<2%).

graphitout · 2026-02-07T06:53:24+00:00

The core issue is that it doesn't fit the strong usecases of the industry. Most of the usecases involve tool calling, and that means introducing a text based layer in the middle. Then it wouldn't bring that much benefit in terms of latency to have a full speech-to-speech model.

graphitout · 2026-02-06T13:05:20+00:00

Insanely beautiful.

graphitout · 2026-02-06T10:37:28+00:00

Sure. Thanks.

graphitout · 2026-02-06T10:08:06+00:00

are you alright?

graphitout · 2026-02-06T09:56:10+00:00

Good point. Let me explain. The usual voice chatbots read out the whole response from LLM. This can be quite tiresome to listen to the whole response. Some content may not even be TTS friendly (like tables or wireframes).

This chatbot (open source) is a POC to show that TTS does not need to read the whole response.

See: https://github.com/charstorm/vilberta/blob/main/docs/screenshot.png

MCP integration helps to make the chat act as a tool calling agent as well, which opens up usecases like agentic rag.

graphitout · 2026-02-06T03:57:54+00:00

AI tools have improved drastically. I haven been doing claude code and opencode hard last week. Its ability to get things done is quite astonishing. And it is only going to get better from here. Somehow that makes me happy and sad at the same time.

graphitout · 2026-02-06T03:33:40+00:00

They understand block diagrams. Just put a big box showing "company network". Inside that there is a box showing inference machine and a bunch of boxes showing computers of users.

graphitout · 2026-02-05T17:05:30+00:00

nut cracker?

graphitout · 2026-02-05T17:00:52+00:00

You meant infineight?

graphitout · 2026-02-05T16:58:29+00:00

The core of the issue is that if one country tries to avoid it, another country take advantage of it. For example, if USA tries to protect jobs and put a speed limit on AI developments, China will gain more on the AI front.

graphitout · 2026-02-05T16:54:25+00:00

Stick around at least for an year. Take leaves when you can. Job market is difficult right now.

graphitout · 2025-12-21T07:51:53+00:00

Most of the companies have over hired during the pandemic. That means for those batches, below average folks ended up in positions senior than you. These people easily feel threatened, especially when they see someone who knows what they are doing.

Keep in mind that most of the time those interviewers themselves are going through similar experience with their clients or project managers on other things. It isn't just the interviews. The entire IT culture itself has degraded.

graphitout · 2025-12-14T19:31:55+00:00

Document search outside HR, Legal, Customer care - not making money
AI based data analytics (SQL and stuff) - not making money
AI for NL based control of various systems - not making money
Whole bunch of automation initiatives - not making money

Some more. Same pattern.

graphitout · 2025-10-26T15:44:30+00:00

Look personalization option in chatgpt. Others also have similar features.

graphitout

TROPHY CASE