Is Vibe coding allowed?

[Dhrubajyoti930]

Learning Through "Vibe Coding" & Project Iteration: Anyone Else?

Hi everyone!

I wanted to share a bit about my current learning journey and see if anyone else takes a similar approach, or if you have any advice on the potential pitfalls.

I wouldn’t consider myself highly knowledgeable in programming yet, but I am steadily learning by diving headfirst into new projects and iterating through repeated attempts. Right now, "Vibe coding" is my anchor—it’s the workflow that keeps my momentum high and helps me get the most done.

My Focus: Aesthetics & Visuals

Because I'm learning as I go, I intentionally set boundaries for my projects:

• Visual-First: I focus almost entirely on the aesthetics, layouts, and front-end experience.
• No Technical Misdirection: I don't attempt to create educational tools or tutorials through this practice, as I want to avoid spreading potentially misleading or unoptimized technical information.

The Big Question: Could this raise issues down the road?

While this rapid-prototyping approach is incredibly fun and keeps me building, I do wonder about the long-term impact.

• Pros: It keeps engineering blockages from killing my creative spark, lets me test ideas at lightning speed, and I naturally absorb syntax by breaking and fixing things.
• Cons/Risks: I worry about creating a "black box" where things look great but the underlying architecture is fragile, making it hard to debug or scale later.

How do you balance the creative "vibe" of building visual projects with learning solid engineering principles? I'd love to hear how others transitioned from pure aesthetic prototyping to deeper coding practices!

[RishiByte]

@Dhrubajyoti930 Vibe coding is absolutely allowed here. 🚀

In fact, many contributors start by building, experimenting, and learning through iteration. The important part isn't how you begin—it's that you're actively learning and improving with each contribution.

Your approach of focusing on UI/UX and visual projects while avoiding educational content you're not confident about is a responsible way to learn.

The main thing to watch out for is exactly what you mentioned: as projects grow, understanding fundamentals like component architecture, state management, debugging, performance, and Git workflows becomes increasingly important.

My recommendation is:

Keep building fast and experimenting.
Ask questions when something feels like a "black box."
Gradually learn the concepts behind the code you're shipping.
Prioritize code readability and maintainability as your projects become larger.

Everyone's learning journey is different, and building real projects is one of the best ways to gain experience. Looking forward to seeing what you create! 🎉

[Dhrubajyoti930]

Thanks for encouragement!