5 ms·
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
by cannonpalms 9mo ago
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.sh https://github.com/whispem/minikv/blob/main/fix_ci_complete....
- whispem 9mo agoThanks 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.
- suhputt 9mo ago[dead]
- whispem 9mo agoThis 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!
- ritcgab 9mo agoThe commit history of this file is hilarious.
- deleted 9mo ago[deleted]