https://leadershiplighthouse.substack.com/p/i-went-all-in-on-ai-the-mit-study
Why is it finally ready now after ten years of being a barely functional input-only android app?
A few weeks ago I saw nostr:nprofile1qqsr7acdvhf6we9fch94qwhpy0nza36e3tgrtkpku25ppuu80f69kfq9q9kky giving a talk and demo of [Shakespear](https://shakespeare.diy/), 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](https://exocortexlog.com/news/articles/2025-11-25-vibecoding/) to start with,
something even a non-dev could do, then [ceased up](https://exocortexlog.com/news/articles/2025-12-01-fixingvibes/), 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
Discussion
Yeah. A lot of the investment and excitement for the AI coding is based on the faith that it'll get better. Some people expect exponentially so even! Though it looks to me more like diminishing returns on exponentially growing investment really. And to assume it can improve without limits is quite a leap of faith.
Nice too though. So long as you're managing the code itself and not just the UI seems useful.
Yeah all in .