conrs
Joined 9 years ago
Joined 9 years ago
I find in software the more constraints I can find the better the innovation ends up being, and business model is an excellent constraint - even just knowing what a responsible amount of effort is versus the value you anticipate.
Admittedly, I originally misunderstood your product as being more like google sheets - where it becomes a cloud drive of sorts with spreadsheets on top. At which point the risk of losing access to the tool would make adoption very unlikely.
So, I'm building a compatibility layer; something that works with everything - including your own vibe-coded personal CRM.
It's already helping - even something as simple as correlating calendar events with new connections so that you always know where you met someone.
https://tend2thrive.com if you're curious; It's live, so DM me if you'd like an account rather than just hitting the waitlist.
I've built a lot with LLM's, my experience sort of but not really tracks that. I've had to course correct a few bad abstractions but the larger the code base becomes the better it seems to be at reusing things. Maybe this is because of types, or spec-first development (with OpenAPI), or black box integration testing - but also maybe not. But generally I have to think about the abstractions and let the LLM fill in the details with rare exception.
The limit here I think the ancestor comments are getting at is cognitive load, which is real and measured. We only have so much memory to devote to a "stack" when executing, and it's usually quite constrained.
The tool assumes so much. That it is fine to kill a process itself versus just asking you to kill the process. That everyone MUST have passwords in their home directory. It's all meaningless without providing the thing it is running and so no activity is technically safe.
Why do people even get the agent to run the commands it asks to run? You can solve the entire threat vector by running it yourself and giving the agent the output. Claude practically only needs things like sed, awk, and grep. It's a pattern matcher. It's a waste of yours (and its) time to have it run your project.
It is completely feasible, and the battery life - amazing. Even when running a whole pile of Kubernetes services.