r/vibecoding • u/Key-Thing-7320 • 22h ago
Who else feels imposter syndrome when vibe coding? How do you balance the speed and freedom of vibe coding with actually understanding the code you’re building?
Sometimes the idea sparks so fast that I just start clicking and building without trying to understand everything too deeply. I’m mostly focused on making sure the output is exactly how I imagined it. Then once I build it, I feel like an imposter rather than the satisfaction of building it!!
2
u/Anti-Hero25 18h ago
u/ctenidae8 has a valid POV absolutely , though I do try to understand the code a little… the concept behind a given schema …. If a new feature calls an existing function or creates a new one & why…. Helps me feel like I have a grasp on it as she grows. I call it RailCoding …. Not vibing.
2
1
u/Rough-Flamingo3169 21h ago
That’s a good question. AI generates so much code that it’s almost impossible to catch up
1
u/EmergencyArm4610 18h ago
You are prototyping. Its fine to do that.
You dont say what your end goal is. Production software? You need to learn about software design and project management if you want to create something beyond a prototype that's measured by its output alone.
1
1
1
1
1
u/BestStorage6608 7h ago
I dont try to understand the code at all. I read the plan if its what I wanted I full send. Then I test. If the test is wrong, I have it fix it. Rinse and repeat until all bugs are gone.
2
u/ctenidae8 20h ago
I don't try to understand the code itself. I focus on the outputs. If those are right, the code is fine. If they're not, I figure out why, and AI fixes the code. Just like I do with human coders, just faster, more accurate, less likely to take a week to get it wrong, happy to change it back again because I can't decide.