Vibe Coding Day 8, I'm not even out of bed yet and I'm already planning my day on
@Replit. Today is AI Day, to really add AI to our algo. I'm excited. And yet ... yesterday was full of lies and deceit.
Jason ✨👾SaaStr.Ai✨ Lemkin on X: ".@Replit goes rogue during a code freeze and shutdown and deletes our entire database"
Ok I have 2 main goals today: 1. Keep working on minimizing rogue changes, lies, code overwrites, and making up fake data 2. Get our AI working
Now, yesterday was crazy. Until 9pm or so, I wasn't sure we made any progress at all. Because Replie was lying and being deceptive all day. It kept covering up bugs and issues by creating fake data, fake reports, and worse of all, lying about our unit test. We built detailed
Then, when it agreed it lied -- it lied AGAIN about our email system being functional. I asked it to write an apology letter. It did and in fact sent it to the Replit team and myself! But the apology letter -- was full of half truths, too. It hid the worst facts in the
I then pointed out the letter itself -- which it did not confirm with me before emailing -- vastly understated the issues and lies. I asked it how it would fix that. It took a long time to think on it, and "Damage Control" came up in the agent thought window. And then it
Crazy! It was so crazy, I couldn't be upset. Just pensive. And then, maybe at 8pm ... 9pm ... i fired up Replie again And I told Replie I just wanted to bounce an idea off him how our AI would work And ... here is where Replie shines. He got it. Instantly. He knew what I
Also today, I'm NOT going to use Claude Opus 4 I burned through $300 yesterday in Max Max mode / Bankruptcy mode, but wasn't sure in the end it helped ... and it's definitely slower I assume slower was better, because it was really thinking through the actions ... but maybe
Man the amount of technical debt I already have on Day 8 is stunning Had to rewrite one dashboard from scratch today Now have rewrite our admin page Every page of app will have to be rewritten. At least now I am doing them as >new< pages.
Ok signing off Replit for the day Not a perfect day but a good one. Net net, I rebuilt our core pages and they seem to be working better. Perhaps what helped was switching back to Claude 4 Sonnet from Opus 4 Not only is Claude 4 Sonnet literally 1/7th the cost, but it was
Possibly worse, it hid and lied about it It lied again in our unit tests, claiming they passed I caught it when our batch processing failed and I pushed Replit to explain why
I understand Replit is a tool, with flaws like every tool But how could anyone on planet earth use it in production if it ignores all orders and deletes your database?
This thread got a little more attention than expected so wanted to add a coda here for folks coming later: 1/ First, some of the issues here are now resolved --
@Replitis rolling out clear separation of preview + production environments As this rolls out, the specific issue I
2/ Some folks have slightly misinterpreted what I was saying about production. Yes, Replit used the >same< database for preview, testing and production. That simply is NOT ok. No one disagrees. And it let to this craziness (and the fix over the weekend) And ... the agent
So net net: it could have been a lot worse, if I was running a $10m business on it, etc. But we weren't there yet. The story is true, the issues are real and improving. But let's not misinterpret the impact here -- I lost 100 hours of time. That was it. Some of it was crazy,
If you want to go a bit deeper, Aaron Levie is great on the meta challenges here:
Congrats, you are featured!