zlacker

[return to "Show HN: Minikv – Distributed key-value and object store in Rust (Raft, S3 API)"]
1. riku_i+N1[view] [source] 2026-01-17 19:52:40
>>whispe+(OP)
Interesting chronology:

Feb 2025: first encounter with coding

oct 2025: started learning rust

Jan 2026: production grade distributed kv store with transactions, enterprise security, durability, etc

◧◩
2. whispe+L2[view] [source] 2026-01-17 20:00:26
>>riku_i+N1
Thanks a lot for your comment!

I’ve put a lot of work into this over the past year—learning from established open source projects and carefully testing every feature to build something robust and reliable. For now, this is still a passion and learning project, but I do hope that, eventually, it can mature enough to be used in real-world production—maybe even in enterprise contexts someday.

There’s still a long way to go, and I’m definitely open to feedback and suggestions from anyone who’d like to help me improve.

◧◩◪
3. riku_i+d3[view] [source] 2026-01-17 20:02:47
>>whispe+L2
main question is what % of code is yours and what % is generated by AI?
◧◩◪◨
4. whispe+J3[view] [source] 2026-01-17 20:07:06
>>riku_i+d3
Good question!

All the code, architecture, logic, and design in minikv were written by me, 100% by hand. I did use AI tools only for a small part of the documentation—specifically the README, LEARNING.md, and RAM_COMMUNITY.md files—to help structure the content and improve clarity.

But for all the source code (Rust), tests, and implementation, I wrote everything myself, reviewing and designing every part.

Let me know if you want details or want to look at a specific part of the code!

◧◩◪◨⬒
5. cannon+td[view] [source] 2026-01-17 21:10:11
>>whispe+J3
You left behind a script clearly written by your LLM tool that patched some problems in your code. It's undeniable.

I'm all for using the tools available, but I don't understand lying about it.

https://github.com/whispem/minikv/blob/main/fix_ci_complete....

◧◩◪◨⬒⬓
6. whispe+gh[view] [source] 2026-01-17 21:38:22
>>cannon+td
This script was actually written manually to automate some repeated local fixes—mainly to speed up my workflow and make sure patches were applied consistently (and safely, with backups).

The colorful output and detailed logging are just for clarity and UX; I tend to over-comment my scripts out of habit—no AI tools were involved here (nor elsewhere in the code).

But I get why it might look generic—happy to explain any section line by line if you want!

[go to top]