A new kind of project started showing up in our inbox this year: 'We built this app with AI and it mostly works, but...'
Mostly works. That's the phrase every time.
The founder vibe-coded an MVP in a weekend. Customers signed up. Then reality arrived: data gets corrupted under concurrent users, there's no real authentication, the codebase is 40 files of duplicated logic no one can follow, and every fix the AI suggests breaks two other things.
Here's the part most people get wrong: the answer is usually not 'throw it away and hire devs to rebuild it properly.' The app validated the idea. Real users depend on it. That's worth preserving.
What it needs is a rescue, not a funeral. Stabilize the data layer. Add real auth. Untangle the duplication one module at a time while the app keeps running. The same incremental playbook we use on 15-year-old ASP.NET systems works on 15-week-old AI-generated ones. Technical debt is technical debt.
If you vibe-coded something that's now carrying real customers and real risk, let's talk before it breaks at the worst possible moment.
devinstance.net/services/mod…
The most expensive modernization project is the one that ships nothing for 18 months and then breaks on cutover day.
We see it all the time. A business runs on an aging ASP.NET app that still works. Someone proposes a full rewrite. The estimate doubles. The timeline triples. Tribal knowledge gets lost. Edge cases the old system handled silently start showing up as bugs in production.
There's a better path: modernize incrementally. Refresh the UI without touching the backend. Migrate to modern .NET piece by piece. Clean up the data access layer where it actually hurts. Each step delivers value. The business keeps running. Risk stays bounded.
That's what we do at devInstance. Assess, roadmap, execute, no flipping a switch on day one.
If your team is staring down a 'we have to rewrite this' conversation, talk to us first.
devinstance.net/services/mod…
Over $200B of western US energy infrastructure is breaking ground through 2030. The contractors building it are still classifying CBA hours by hand on Friday afternoons.
Tentrie automates the classification at point of entry, on the daily field ticket.
tentrie.com/?utm_source=twit…
4 AM trouble call. Crew rolls before sunrise. By end of day the ticket has shift differential, double time, subsistence, and a meal penalty. All four classified before it leaves the field.
That's what Tentrie does. For #IBEW/#NECA outside line contractors.
tentrie.com/?utm_source=twit…
Your AI-generated MVP works fine.
Until it doesn't.
After 30 years cleaning up "fine until it wasn't" code, here's my honest take on vibe coding for non-technical founders 🧵
The founders who win this cycle won't be the ones who shipped the most polished AI-generated app.
They'll be the ones who got to 10 paying customers fastest, and knew enough to fix the foundations before the 11th broke them.