🔥
Mar 30 • 🎙️ General discussion
Vibecoding: What’s the hardest part of that process for you?
I came across a post in another group that got me thinking, and I wanted to bring it here 👇
For those of you who vibe code with tools like Loveable or Bolt, then go back and try to actually understand what was generated…
What’s the hardest part of that process for you?
Is it:
- Connecting how everything works together?
- Understanding why certain decisions were made?
- Debugging when something doesn’t behave how you expect?
- Turning it into something you could confidently rebuild on your own?
I’ve noticed there’s a really interesting phase after generating code where things start to “click” (or don’t), and I’m curious how you all approach that.
Drop your experience below 👇 I’m exploring an idea and would love your input.
10
23 comments
Vibecoding: What’s the hardest part of that process for you?
skool.com/the-code-zone
Beginner-friendly community to learn Python, HTML, CSS, & JavaScript. We help you become a full-stack developer and offer 1:1 code coaching.
Leaderboard (30-day)
1
+67
2
+59
3
+56
4
+55
5
🔥
+51
Powered by