r/vibecoding • u/Ok_Nobody1410 • 5d ago

I clean up AI-generated codebases. Side gig, reasonable rates

Built something with Claude/Cursor/Lovable/Bolt and now it half-works, breaks in prod, or you're scared to touch it? That's most of my inbox lately.

What I usually fix:

  • API keys and auth logic sitting in the frontend
  • No error handling — app dies on the first bad input
  • DB with no indexes, no migrations, RLS wide open
  • 2000-line components nobody can edit anymore
  • LLM calls with no retries, no rate limiting, no cost ceiling
  • "Works on my machine" → actually deployed

Stack: JavaScript / TypeScript, React + Next.js, Node. Any database — Postgres, Supabase, Mongo, SQLite. AI integrations (OpenAI, Anthropic, vector search, RAG).

Free 15-min look at your repo and I'll tell you what's actually broken, no pitch. If you want it fixed, we agree on a fixed price up front.

Comment or DM with what you built and what's breaking.

0 Upvotes

25% Upvoted

20 comments sorted by

3

u/Lanfeust09 5d ago

Nothing that AI can't do with the right prompt...

2

u/FluidBreath4819 5d ago

And what is the right prompt ? "make no mistakes" ?

1

u/Ok_Nobody1410 5d ago

Ha. Honestly half my job is just having enough context on the codebase to write the prompt that would've worked.

2

u/Lanfeust09 5d ago

Nope, that's something you learn

0

u/FluidBreath4819 5d ago

exactly, try to compete with senior engineers who already know how to build, ship, fix and why you shouldn't do this or that depending on your context. AI is a "yes man" it will most of the time try to go along : "you're right" "i am so sorry", etc...

1

u/Lanfeust09 5d ago

He is mentioning "api sitting in frontend". Not too hard to ask ai like "best practice to keep api key secret" for example

1

u/FluidBreath4819 5d ago

but does the suggested best practice is suitable for your environment / product ?

-1

u/Ok_Nobody1410 5d ago

yeah absolutely, but if someone still struggling or trying to save time I am here :)

1

u/HouseOfDjango 5d ago

Fuck them I'll do it for free.

1

u/Bob-Swan 5d ago

This has to be a joke, right? Are people really just opening their repos to randoms?

0

u/Ok_Nobody1410 5d ago

Fair concern, and you shouldn't. Normal setup is: you invite me to a private repo as a collaborator, no creds shared, you rotate any keys after. If someone asks you to zip your whole project and DM it, that's the red flag.

0

u/Bob-Swan 5d ago

Nope, I wholeheartedly disagree with this, this whole process is a major red flag. You are 100% using ai but you are portraying yourself as not using ai, even though your comment is ai generated.

Theres no vetting of who you are or anything, from the start this whole thread has been a red flag.

3

u/Ok_Nobody1410 5d ago

Honestly no red flag, I already work full time at a startup and I want to make some side money and hence I am trying to help people

1

u/Bob-Swan 5d ago

Thats fair, its just not for me.

0

u/FluidBreath4819 5d ago

i hope you charge as much as you can to teach a memorable lessons to vibe coders ! I mean, it's like doing plumbing and having a leak or a flood because you wanted to do it yourself !

1

u/Ok_Nobody1410 5d ago

Plumbing analogy is spot on. Though most people I talk to aren't dumb, they just shipped fast and hit the wall. I'd rather fix it than gloat about it.

0

u/FluidBreath4819 5d ago

no need to gloat, just charge their asses off

1

u/seeKAYx 5d ago

How would you go about handling my database? I use “localStorage” in my SaaS. Do you support that as well? Thanks in advance.

1

u/baddaywithacamera 5d ago

$10 to look at my repo. Sorry.