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](

Shakespeare - Open Source AI Builder
Build custom apps with AI assistance using Shakespeare, an open-source development environment
), 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](

Exocortex Blog
Vibe Coding - Exocortex Blog
A review of Shakespeare.diy for vibe coding
) to start with,
something even a non-dev could do, then [ceased up](

Exocortex Blog
Fixing The Vibes - Exocortex Blog
Fixing the problems introduced by vibe coding
), 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 β