The first time a real developer looked at my vibecoded project, what happened?
Finally showed my cofounder's technical friend the app I'd been building solo with Claude Code for two months. I was proud of it, it worked, users were paying for it, I felt like a real founder walking him through the codebase.
He got quiet about four minutes in. Not rude about it, just quiet in that specific way where you can tell someone's recalculating their opinion of you in real time. Eventually asked why there were three different ways of handling API calls scattered across the codebase, and I didn't have an answer beyond "that's probably just whatever the agent decided each time I asked for something new."
Didn't feel great. The app still works, still makes money, still solves the problem it was built for. But something about watching someone who actually knows the craft better than me raise an eyebrow at it made me feel like a fraud for about a week, even though nothing about the product itself had changed.
Has this happened to you, showing your vibecoded work to someone with real engineering chops? What did they catch that you'd never have caught yourself, and did it actually change how you build going forward, or did you just quietly feel bad about it and move on like I did?
Replies
I'm the guy who goes quiet at minute four, so let me tell you what's actually happening in that silence, because it isn't what it felt like.
It's not "this person is a fraud". It's that I've started holding your whole system in my head at once, and I've hit a seam, three ways to call the API, and I'm trying to work out if there's a reason or if it's just history. That's the entire tell. Working code that makes money is not in question. Consistency is, because inconsistency is where the next bug hides.
And here's the part that should take the fraud feeling off you: a real engineer moving fast solo produces the exact same three ways. The difference isn't that they'd never do it. It's that they know to go back later and collapse it into one. That's a habit, not a talent, and it's learnable in an afternoon.
So the thing I'd change going forward isn't how you build, it's adding one pass: every so often, ask the agent to find where the codebase does the same thing more than one way and pick a single pattern. The eyebrow was information, not a verdict. It just meant nobody had done the consolidation pass yet.
What did he catch that stuck with you the most?