DEV Community

Cover image for "AI Remediation": Is Fixing Vibe-Coded Sites the New Web Dev Job, or a Dead End?
Hannan Shoukat
Hannan Shoukat

Posted on AI-assisted

"AI Remediation": Is Fixing Vibe-Coded Sites the New Web Dev Job, or a Dead End?

A thread on r/webdevelopment asked whether web development is still worth learning in 2026 (Webdesigner Depot rounded up the replies). One reply stuck with me. The commenter suggested developers position themselves as an agency that offers "AI Remediation": fixing sites that a founder or a staff member vibe-coded without knowing how to review, host, secure or make them accessible.

The idea is simple. More people can now generate a website in an afternoon. Some of those sites will have broken mobile forms, slow pages, accessibility gaps or security holes, and someone will have to fix them.

I can't decide whether that's a real opportunity or a trap.

Why it might be the job:

  • There will be a lot of these sites, and most owners won't know what's wrong, only that "it doesn't work on my phone."
  • Debugging someone else's messy code is a real skill. AI-generated code that nobody fully read is messy code with extra confidence.
  • It pushes developers toward the parts AI is weaker at: judgment, security, performance and knowing what "done" means.

Why it might be a dead end:

  • If AI builds sites badly today, it may fix them well next year. Remediation could be a short window, not a career.
  • Cleanup work is often underpaid. Clients who chose the cheapest way to build may also want the cheapest way to fix.
  • "Fix this AI site" can turn into "rebuild this AI site," and that's a hard conversation when the client thinks it's 90% finished.

The same thread had a line I keep coming back to: "You should never have an AI write something you could not write yourself." If that's true, the people fixing AI sites will be the ones who learned the fundamentals the slow way.

So, what do you think?

  • Have you been asked to fix a vibe-coded or AI-built site yet? What was actually wrong with it?
  • Would you market yourself as "AI remediation," or does that sound like a niche that disappears in two years?
  • If you've done this work, did you fix it or end up rebuilding?

I'd especially like to hear from freelancers and agency folks, since you're the ones getting these calls.

Top comments (4)

Collapse
 
jes_p_d4f61f7aa2ec405a418 profile image
Dev_PJS •

Dead end vs job is the wrong fork, I think — it's a demand signal either way. The pattern I trust: don't build supply and hope; look at what people are already asking to have fixed, and let that shape the offer. Vibe-coded sites are a growing pile of exactly that: owners who can generate but can't review, secure or ship. And notice the durable part of the work isn't the fixing. It's the reviewing — the judgement about what's broken, what's risky, what's fine. Generation keeps getting cheaper. The person who can look at generated work and say what's wrong with it is selling the thing that doesn't. Whether that's a job or an agency shape matters less than that the demand is real and already phrased by buyers.

Collapse
 
hannanshoukat profile image
Hannan Shoukat •

"Selling the thing that doesn't get cheaper" is a better framing than the one I started with. Fixing will get automated eventually. Judging what's risky and what's fine is much harder to hand off. And you're right about the demand side: owners don't search for "AI remediation." They say "my site doesn't work on my phone" or "the contact form stopped sending emails." So maybe the real positioning question isn't the label, it's matching the words owners already use. Have you seen that kind of phrasing show up in actual requests yet?

Collapse
 
officialmailkr profile image
오피셜메일 •

수정 의뢰가 전체 재구축으로 바뀌는 경계가 핵심이라는 생각이 들어요. 처음부터 고정된 수리 견적을 내기보다, 재현 가능한 결함 목록과 유지할 부분·교체할 부분을 정리하는 진단 단계를 분리하면 기대치 차이를 줄일 수 있겠어요. AI가 만든 코드인지보다 수정 후 어떤 사용자 흐름을 검증할지 합의하는 편이 서비스 설명도 더 오래갈 것 같습니다.

Collapse
 
hannanshoukat profile image
Hannan Shoukat •

That's a really practical way to frame it. A diagnosis step first, with a list of reproducible defects and a keep-or-replace call for each part, turns "is this a fix or a rebuild?" into something the client can see before any quote. I also like agreeing on which user flows get verified after the fix. "Checkout works on mobile Safari" is a promise a client understands. "The code is cleaner now" isn't. Have you seen anyone charge for the diagnosis separately, and do clients actually pay for it?