I love this approach. Great work. Building helpful, accurate has been the second hardest part of building my employer’s internal app. (The most difficult thing has been reaching consensus on processes.)
Commenter:
> What % of the code is written by you and what % is written by ai
OP:
> 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!
Oof. That is pretty damning.
———
It’s unfortunate that em-dashes have become a shibboleth for AI-generated text. I love em-dashes, and iPhones automatically turn a double dash ( -- ) into an em dash.
The author felt pressure to build an explosive startup with tons of early funding. For those feeling similar pressure, look into the concept of “slow burn startups.” These are startups that stick around and make long-term impact.
Are there tradeoffs between individual-element and group-element mindsets with regards to project scale? Does the group-element/global architecture mindset require holding the whole program in my head? Is that even possible for large projects?
I have no experience working in C. Obviously, some of the biggest and most important codebases on earth are C.
reply