tekBlueprint

A while ago there was a post about agentic development for a project. This is a follow-up, but in a slightly different, more practical direction. The task was an MCP service / KAG / GraphRAG in Go. After completion, it “unexpectedly” turned out that the project contained a fatal flaw in the shape of the letter G. So a deliberate decision was made to migrate to Rust. This venture required changing the tech stack, the libraries, the algorithms, implementing an LSM-like mechanism for the vector database, and so on. In other words, it was not a mechanical port but a migration with substantial rework.

A spontaneous article on agentic development, written after some time and attempts at using this approach. Below are general theses, some of which I probably already touched on about a year ago. Overall, things turned out as expected. There was no revolution, and the bubble is deflating here and there, even though everyone pretends everything is “on plan”. The promised AGI, for some reason, still hasn’t taken over the world :)

I recently looked at what’s currently being actively promoted in AI development. It gave me some ideas about what’s happening and what will happen to the current tools aimed at improving coding efficiency. If true, it doesn’t look very promising.