Future Plans: I have like ten years of data in my log, converted from those prior prototypes. I will be adding ways to more usefully compare and analyse data going this far back. It could maybe use a milestone function, to track singular events which don't take actual time so don't spread on the grid. Snack tracking and the like. It could likely use a flashcard system, with spaced repetition to review the flashcards, for better memory and recall. Synching between devices might be nice, and lots will suggest doing that through Nostr, but Nostr is a bit public. Would need an encryption layer. Do nostr relays want to relay encrypted data from one user to themselves I suspect Veilid ( ) would be a better option. The "no servers" ethos probably includes nostr relays. Mostly I plan just more and better ways to view the ten years and growing of data I already have. And to do some other things for a bit so my log isn't just full of "Vibecoding Exocortex" 😄 View quoted note →
Why is it finally ready now after ten years of being a barely functional input-only android app? A few weeks ago I saw @Derek Ross giving a talk and demo of [Shakespear](), a Chrome app for vibe-coding. Explain the app you want, and the model you select will build it. Don't even need to be a dev they reckon. So I figured I'd give it a try. Start again from scratch, import the old data. In about a week of work this app has progressed far beyond the prototypes that spent more then ten years as half-running shoddy input-only systems that I couldn't be arsed to expand further. It went [pretty well]() to start with, something even a non-dev could do, then [ceased up](), unable to really understand the codebase it'd written until I spend a fairly long day manually cleaning up it's mess. So Shakespeare (and presumably all the other tools I haven't tried) seems okay for a non-dev to prototype a small app but currently the models are writing code so sloppy that they can't then later understand it themselves. Still needing a dev's guiding hand to keep it from repeating itself or creating complex unorganized unmanageable code. #vibeCoding #shakespeare View quoted note →