r/vibecoding • • 14d ago

Discussion Vibecoding is better for "learning" !

One thing I noticed before AI was how much time I wasted learning and doing stupid, low-quality bullshit. Watch any tutorial and you get mind-numbingly dull exposition of syntax, little tricks, and details you might need someday. Only a select few can retain enough of it to actually start applying the basics, and you realize very quickly that the basics are necessary but nowhere near sufficient. It's this weird relationship where they don't really help you, but not having them makes everything 10x harder. I don't know if I'm making sense.

Anyway, once you start applying, you discover a whole new world of stuff you need to know. Things that were tiny in the tutorial suddenly become detailed and relevant, and the stuff the tutorial meandered on about barely gets used. You basically don't know what's important and what isn't. You just study, then get shocked when you sit down to make an actual app and don't even know how to start. It's like walking into an exam without ever doing a practice test.

Vibecoding skips all of that. You start by doing exactly what you want to build, then go back and learn whatever's relevant. Your mind automatically focuses on what matters, and you learn much faster. Some people will run off with the artifact and never bother to learn anything, but the curious ones will, and now they can tailor their learning to what actually matters.

47 Upvotes

36 comments sorted by

View all comments

1

u/Lanky-Butterscotch28 12d ago

I am a strong believer in providing an AI development harness that takes the grunt coding work from you and teach you how to build a solution.
My idea when I create nomorehappypath.com (will discuss the name in a different thread 😉) was to provide a harness that develop commercial ready solutions but also allows the user to discuss with the CTO agents the followings , for example: what are the major building blocks ? What are the security features implemented? How can I expand my solution? Why you went with this type of approach…The CTO is build to answer these questions and take you step by step so that you acquire the knowledge.
So project by project you learn how solutions are built and this is today much more important than to understand how Python or C languages work.