whispem

5 ms·

1. 1.▲
   Show HN: WhispHub CLI – push your projects to WhispHub from the terminal(crates.io)

   1 points by whispem 4mo ago|0 comments
2. 2.▲
   Show HN: Whispem – a small, readable interpreted language(github.com)

   1 points by whispem 7mo ago|0 comments
3. 3.▲
   by whispem 8mo ago

   Yes, in minikv, I set up GitHub Actions for automated CI. Every push or PR triggers tests, lint, and various integration checks — with a typical runtime of 20–60 seconds for the core suite (thanks to Rust’s speed and caching). This means th
4. 4.▲
   by whispem 8mo ago

   minikv actually supports a fully S3-compatible API (PUT/GET/BATCH, including TTL extensions and real-time notifications). By default, the storage engine is segmented/append-only with object records in blob files, not “one fil
5. 5.▲
   by whispem 8mo ago

   Yes, I do split my working tree into separate commits whenever possible! I use interactive staging (git add -p) to split logical chunks: features, fixes, cleanups, and documentation are committed separately for clarity. Early in the project
6. 6.▲
   by whispem 8mo ago

   Absolutely: for all meaningful work I prefer small, logical commits using git add -p or similar, both for history clarity and for reviewer sanity. In initial “spike” or hack sessions (see early commits :)), it’s sometimes more monolithic, b
7. 7.▲
   by whispem 8mo ago

   There’s not an “official” image on Docker Hub yet, but the repo ships with a ready-to-use Dockerfile and a Compose cluster example. You can build with docker build . and spin up multi-node clusters trivially. Static Rust binaries make the
8. 8.▲
   by whispem 8mo ago

   Very relevant question! The memory profile in minikv depends on usage scenario and storage backend. - With the in-memory backend: Every value lives in RAM (with HashMap index, WAL ring buffer, TTL map, and Bloom filters). For a cluster with
9. 9.▲
   by whispem 8mo ago

   Thanks for the feedback and for the question! A number of choices in minikv are explicitly made to explain distributed system ideas clearly, even if not always optimal for hyperscale prod environments: - Raft + 2PC together, as above, so pe
10. 10.▲
    by whispem 8mo ago

    Thank you for this sharp and detailed question! In minikv, both Raft and 2PC are purposefully implemented, which may seem “overkill” in some contexts, but it serves both education and production-grade guarantees: - Raft is used for intra-sh
11. 11.▲
    by whispem 8mo ago

    Thanks!
12. 12.▲
    by whispem 8mo ago

    Yes! I'll check as soon as possible
13. 13.▲
    by whispem 8mo ago

    No, I was helped (.md files only) by AI to rewrite but the majority of the doc is written by myself, I just asked for help from the AI for formatting for example.
14. 14.▲
    by whispem 8mo ago

    I don't see the problem to be honest
15. 15.▲
    by whispem 8mo ago

    Thanks a lot! I make distinct commits "every 30s" because I'm focused and I test my project. If the CI is green, I don't touch of anything. If not, I work on the project until the CI is fully green.
16. 16.▲
    by whispem 8mo ago

    I had the opportunity to request a review of my first post (which was flagged) following my email to the moderators of HN. I didn’t use AI for the codebase, only for .md files & there's no problem with that. My project was reviewe
17. 17.▲
    by whispem 8mo ago

    Hello! Thank you for your message. I don’t know this project, do you have a GitHub link maybe?
18. 18.▲
    by whispem 8mo ago

    Yes, I know. I had the opportunity to request a review of my first post (which was flagged) following my email to the moderators of HN. After checking, the moderator told me to redo a post because indeed I was wrongly flagged by some peop
19. 19.▲
    Show HN: Minikv – Distributed key-value and object store in Rust (Raft, S3 API)(github.com)

    71 points by whispem 8mo ago|38 comments
20. 20.▲
    by whispem 8mo ago

    I already said that the code was 100% handwritten but the .md files and scripts. I don't see the problem here.
21. 21.▲
    by whispem 8mo ago

    Yes, .md files are authored with the help of AI tools but not the code at all. The code is 100% by me.
22. 22.▲
    by whispem 8mo ago

    My work has been reviewed, don't worry about that. But it is not vibe coded at all.
23. 23.▲
    by whispem 8mo ago

    I didn't use AI or any prompt with LLMs.
24. 24.▲
    by whispem 8mo ago

    So you trust random comments? I know what I'm talking about.
25. 25.▲
    by whispem 8mo ago

    Some people tell I used LLMs but it's not true. I learned, a lot. It was long but it works now.
26. 26.▲
    by whispem 8mo ago

    I didn't use LLMs for my projects. I learned by myself.
27. 27.▲
    I went from literature/language to Rust systems programming in under a year(github.com)

    14 points by whispem 8mo ago|11 comments
28. 28.▲
    by whispem 8mo ago

    Hi HN, I’m Emilie (Em’ on GitHub: https://github.com/whispem ). My background is in literature and linguistics – I spent most of my pre-2025 life far away from computers. I really started programming in January 2025 through
29. 29.▲
    by whispem 8mo ago

    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
30. 30.▲
    by whispem 8mo ago

    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