Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ViktorKuz
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
4 ms
·
1.
▲
Hi, I'm Viktor.I wasn't a programmer. I didn't build apps. I didn't write code
1 points
by
ViktorKuz
10mo ago
|
1 comments
2.
▲
80.1 % on LoCoMo Long-Term Memory Benchmark with a pure open-source RAG pipeline
1 points
by
ViktorKuz
10mo ago
|
0 comments
3.
▲
Show HN: Change the model. Same output. The pipeline decides. VAC Memory System
1 points
by
ViktorKuz
10mo ago
|
0 comments
4.
▲
My experience learning AI from scratch and why it changed how I see coding
1 points
by
ViktorKuz
11mo ago
|
0 comments
5.
▲
Show HN: VAC Memory – 80.1% LoCoMo accuracy vs. Mem0's 68%
(github.com)
2 points
by
ViktorKuz
11mo ago
|
0 comments
6.
▲
by
ViktorKuz
11mo ago
Is a non-generative, retrieval-only architecture (excluding LLMs from the search steps) the optimal solution for building highly reliable and cost-effective personal memory systems?
7.
▲
by
ViktorKuz
11mo ago
More and more developers are switching to local LLMs - and the 1 reason is simple: security. Your data never leaves your machine. Zero risk of leaks. Meanwhile, we’ve seen dozens of high-profile incidents with cloud providers dumping privat
8.
▲
Show HN: MCA-Entity Coverage as a Memory Retrieval Gate
(github.com)
1 points
by
ViktorKuz
11mo ago
|
1 comments
9.
▲
by
ViktorKuz
11mo ago
true the bottleneck was never "typing code", it was aligning business logic, constraints, and changing requirements. What AI does change is the cost structure: instead of one programmer spending a week, you can spawn 10 parallel a
10.
▲
They Say AI Will Replace Programmers. I Think AI Will Mass-Produce Them Instead
(github.com)
2 points
by
ViktorKuz
11mo ago
|
2 comments
11.
▲
by
ViktorKuz
11mo ago
Thanks for the kind words about VAC Memory System! Love what you're doing with ChatIndex - the hierarchical tree approach is really smart! Preserving all raw data while adding semantic navigation layers is an elegant solution. We
12.
▲
I built an open-weights memory system that reaches 80.1% on the LoCoMo benchmark
2 points
by
ViktorKuz
11mo ago
|
2 comments
13.
▲
80.1 % on LoCoMo Long-Term Memory Benchmark with a pure open-source RAG pipeline
3 points
by
ViktorKuz
11mo ago
|
0 comments
14.
▲
Show HN: Memory System Hitting 80.1% Accuracy on LoCoMo (Built in 4.5 Months)
(github.com)
2 points
by
ViktorKuz
11mo ago
|
0 comments