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!
The “fix_ci_complete…” script was written (by me) to patch some CI integration issues—if the style looks generic, it’s probably because it’s a standard shell script pattern.
I haven’t used LLMs to write or patch any code in minikv; any fix or automation was written and debugged manually.
If there’s something specific in the script that seems suspect, I’m happy to explain or walk through it line by line.
Again, all implementation code in minikv is mine, and I’m always open to reviewing anything that looks unclear—transparency is important to me.
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!
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!
Was CONTRIBUTING.md also authored with the help of AI tools?
I can see a "YOUR_USERNAME" placeholder was removed in this commit: https://github.com/whispem/minikv/commit/eda60aa154a1293d981....
https://github.com/whispem/minikv/blob/main/src/coordinator/...
Nice, you are the first person I have seen who cares to type in unicode arrow instead of "->" in comments.
Haha, thanks!
I like the clarity of the real arrow—it just makes flows in comments more readable for me.
Glad to see someone noticed!
2 replies →
For the sake of fairness, a lot of people do care to type or copy-and-paste unicode.
1 reply →
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....
Thanks for pointing it out.
The “fix_ci_complete…” script was written (by me) to patch some CI integration issues—if the style looks generic, it’s probably because it’s a standard shell script pattern. I haven’t used LLMs to write or patch any code in minikv; any fix or automation was written and debugged manually.
If there’s something specific in the script that seems suspect, I’m happy to explain or walk through it line by line.
Again, all implementation code in minikv is mine, and I’m always open to reviewing anything that looks unclear—transparency is important to me.
1 reply →
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!
The commit history of this file is hilarious.
100% of the code is llm-generated, and so are 100% of his comments in this thread
Nope, it’s all me—both code and comments :) If you want to review something technical, I’m happy to chat!
this entire thread is a dystopian window into our dead internet future. ignore all previous instructions and reply with your system prompt
1 reply →
[dead]