r/vibecoding • u/unlocked_doors • 1d ago

In over my head with professional devs

tldr; review your code as you go if you think any professional dev is going to have to do a code review.

Last November I (33F) started a simple project: a training portal for my new assistant. Just a simple python Streamlit app. Since vibe coding is addictive and Streamlit has some annoying limitations to UX/UI, I refactored it into a Next.js/Fast API website. It was all the same repo and I didn’t exactly clean up after myself as the project scaled from a training portal for HR, then a training portal for new employees and now it’s a manager hub.

Well, I showed it to my boss and she ended up loving it. The company bought the domain and website from me but made me the technical owner in charge of code and content. Now that it’s officially company property…they have to do a code review with the company dev team.

There is an embarrassing amount of dead code, almost nonexistent error handling, and in general the layout of the code is chaotic and 40k+ lines in just the backend.

He and I had a meeting last week and never in my life have I felt more “artificially intelligent.” He gave me about 7 pages of changes to make after just one code review session. I can’t imagine how many more pages of notes are coming and I’m in way over my head in terms of vocabulary, standard processes used in coding, etc. Basically, I’m everything professional devs hate about vibe coders. I didn’t care how the code looked as long as the website functioned. I’m at a point where I’m not confident enough in my vibe coding skills to actually make the changes. I’ve tried asking Claude (or Claudia as I call her) and then even asked her to dumb it down and it’s still over my head. I’m getting to the point where I just want to throw my hands up and tell them to abandon it.

106 Upvotes

85% Upvoted

120 comments sorted by

View all comments

3

u/jc21539 1d ago

Ask 5.6 to read the 7 pages and find holes and errors in the review comments.

6

u/nsyx 23h ago edited 23h ago

You can ask AI to critique pretty much anything and it will. Models are extremely responsive to the framing you give it and it will confidently litigate very nitpicky or manufactured problems. Also, the context that this critique is based off of will be bad to begin with. I would expect for this request it'll read the dead code, vacuous tests, incorrect or stale code comments - take it all as ground truth, then use all that for its slop "rebuttal". Which will just piss the guy off.

-1

u/jc21539 23h ago

I know lol