What advice would you give yourself starting your Vibe Coding journey?
by•
Hi friends, recently started vibe coding as a way to explore a product that I've been wanting to build for myself and others. I started in the world of V0 and Lovable then into Cursor, but moved away when I felt like I was wasting more credits on debugging and re-providing context. I feel like I've finally hit my stride with Claude Code I would appreciate any tips that you would have given yourself at this point in my journey. Thanks all!
42 views
Replies
Looking back, I'd tell myself to stop over-optimizing early. Shipping something imperfect taught me faster than endless tweaking. Momentum beats precision at the beginning and clarity shows up only after you build, break and rebuild a few times.
Projekt
@chandrshekhar_rawen love it and I agree, I've been launching and learning as fast as I can. Just need more users to learn from :)
Love this journey, very relatable. One thing I wish I’d learned earlier is to treat vibe coding as a prototype accelerator, not the final implementation. Use it to validate UX, workflows, and demand fast, but start locking down architecture, data models, and security boundaries as soon as real users show interest. Also, write down assumptions the AI is making (auth, edge cases, infra defaults) because those become invisible tech debt quickly. Claude Code is great for staying in flow, pair it with small, well-defined prompts and occasional manual refactors, and you’ll get the best of both worlds. Keep shipping 🚀
Projekt
@vickigui great points! I appreciate it, I'm going to definitely take it to heart in particular about looking ahead as my project scales or gains interest. I've hit double digit users and it feels early but I guess not too early to consider if it jumps to any significance. Thank you!