pi_22by7

7 ms·

1.
by pi_22by7 11mo ago
You do use AI! And I do too, I started my work with AI about 2 years after you did, and the experience and opinions I have match yours to a T. However, I have tried AI to do things from scratch multiple times, and the fact still remains th
2.
by pi_22by7 11mo ago
The key insight about bloom filters lacking synergy is excellent. The ~7K document crossover point makes sense because inverted indexes amortize dictionary storage across all documents while bloom filters must encode it linearly per documen
3.
by pi_22by7 11mo ago
Hey HN, I'm the author. I got tired of re-explaining my codebase to Claude and Copilot every session. They forget everything—architecture, patterns, conventions. It's like talking to a goldfish. So I built In Memoria: an MCP serve
4.
Show HN: In Memoria – MCP server that stops AI assistants from forgetting(github.com)
2 points by pi_22by7 11mo ago|1 comments
5.
Show HN: In Memoria – AI memory layer for persistent context in coding tools(github.com)
2 points by pi_22by7 1y ago|0 comments
6.
Show HN: Built a memory layer that stops AI agents from forgetting everything(github.com)
13 points by pi_22by7 1y ago|0 comments
7.
by pi_22by7 1y ago
Nice work on the game! The recording shows it off well. Good thinking using asciinema for this kind of thing. I'd probably be the idiot who types pacman and wonders why it's trying to update my system instead of starting the game.
8.
by pi_22by7 1y ago
This looks really useful for documentation. The text-based approach seems like a huge advantage over screen recordings. Being able to copy-paste commands from a "video" is brilliant. The privacy concern about auto-uploading is a b
9.
by pi_22by7 1y ago
I’m with @NitpickLawyer on this; the scan is cool, but I was hoping for a bit more detail on what’s actually being exposed. Even something like a breakdown of common tool names or clustering by function type would’ve been really insightful.
10.
by pi_22by7 1y ago
oh, for sureee
11.
by pi_22by7 1y ago
Thanks for jumping in, that’s actually really helpful context. Parallelism and selective test execution built-in sounds like a huge win, especially for CI and larger teams. I’ll admit the Scala dependency still makes me hesitate a bit for p
12.
by pi_22by7 1y ago
True. Tests usually dominate the time budget. But from what I've experienced, slow builds still hurt, especially when you're iterating frequently or working across multiple modules. Those 10–20 seconds of wait adds up fast when yo
13.
by pi_22by7 1y ago
So it did the same work that a sitemap does? Interesting. Or maybe more like the opposite: robots.txt told bots what not to touch, while sitemaps point them to what should be indexed. I didn’t realize its original purpose was to manage dupl
14.
by pi_22by7 1y ago
Honestly, I'm getting tired of the endless parade of "better" build tools. Maven works fine for most of what I do, even if it's occasionally painful. Gradle is... well, Gradle has its moments. That said, Mill's perf
15.
by pi_22by7 1y ago
This is a sharp dissection of ‘inevitabilism’ as a rhetorical strategy. I’ve noticed it too: the moment someone says ‘X is inevitable’, the burden of proof disappears and dissent becomes ‘denial’. But isn’t that framing itself... fragile? W
16.
by pi_22by7 1y ago
I built this because I was tired of songwriting apps with subscriptions and ads interrupting my creative flow. It's open source, works offline, and syncs across all platforms. You can try the web demo at flowrite.pi22by7.me Happy to an
17.
Show HN: Flowrite – Why I built a songwriting app instead of paying subs(github.com)
3 points by pi_22by7 1y ago|1 comments