r/vibecoding • • 13h ago

Help/Question Learning normal coding through vibe coding?

Been making an app, because I need it for some stuff working on and automating stuff helps a lot. Using ChatGPT and Claude. Been asking for rundown on terms and such when a change is made to the code, to sort of learn what everything does. I’ve learned a bunch of stuff, but it does happen at a slow pace. Anybody have tips on also learning while vibecoding? Learning to code is sort of a bucket list thing for me

16 Upvotes

20 comments sorted by

8

u/RogerAI--fyi 10h ago

Don’t just ask for a rundown, ask it to create a breakdown in html divided in sections describing fundamentals of what it did and include quizzes in between and smaller (but similar concepts) problems you can solve all in a web based playground. Then spend a good amount of time until you pass it before continuing to the next session.

8

u/PM_ME_UR_0_DAY 10h ago

If you want to learn how to code, read a book or take a course. Your local community college probably has a great beginnes course for very little money. Asking it what it's doing at the time is like trying to learn geography by asking the bus driver what street you're on right now. You'll need to learn the actual concepts of CS, the syntax of the language, and how to think about designing a program. You won't get all that from getting the latest rundown of what it's doing. 

1

u/RemarkableWish2508 6h ago

Depends.

My favorite way of learning coding, has always been the hands-on cowboy approach of getting overwhelmed with more information than I could process. Followed by taking a break to read the reference/manual, followed by skimming over some patterns and best practices.

I hate to spend time reading stuff I don't know what it's going to be used for... and generally retain about 0% of it anyway, while doing it the other way around, tends to land me 90% of more.

0

u/PM_ME_UR_0_DAY 6h ago

I totally do this too, but I don't think it's a great place to start out. Much better for learning new skills after you already have the foundational knowledge. 

0

u/juniperico 6h ago

This doesn’t sound like a very efficient way to learn.

>hate to spend time reading stuff I don’t know what it’s going to be used for…

That’s literally learning anything. Of course you don’t know what’s it for because you haven’t learnt it yet!
Foundational knowledge isn’t obvious at first but makes later learning much more effective.

-1

u/RemarkableWish2508 5h ago

Disagree. Seeing which holes it fits in, gets knowledge locked in place for life. Then, try doing the next "impossible" thing to open spaces for the next step of knowledge.

3

u/SirHC1977 9h ago

I was mostly a Scala developer before I tried vibe coding and was steered towards TypeScript. I learned a lot about TypeScript just by reading the code.

However, I must say, learning TypeScript syntax is the easy part. Understanding how to structure an app, properly apply separation of concerns, and learn architectural patterns are keys to being a successful developer - even if you use AI coding tools. That's where books and courses can help you.

3

u/MattSenter 10h ago

wow i love this. developer of 30+ years here. to me "vibecoding" is like downloading new info from the matrix directly into my brain. areas i never explored are just an idea away. i love that you are trying to understand how things work. the things you really need to be focusing on IMO are security and patterns. the underlying language is pointless at this point. programming concepts are what you need to understand. workflows, optimizations. if you can start learning the approach your agent is taking and then nudging it toward a "better" way, you are going to outperform all others with minimal effort. what i would do if i were you is ask it why it made the decisions it made, then start thinking defensively and suggesting potential flaws. when you engage it in a discussion you will start to see where the holes are. simple example: a lot of newcomers think client-side validation is all you need, but you also need server-side validation.. can't just trust what the client sends. so if you start asking your agent "what happens if..." and "could someone do x..." you can REALLY start learning some really important concepts. think like a "hacker." how would you poke holes in the architecture? once you can start telling your agent how to build something, you will start getting real results.

1

u/jimmiebfulton 6h ago

Don't be se it as a crutch. You only learn things by doing them... essentially doing a machine learning process on your own brain. If you truly want to progress beyond slop, you MUST actually know how to really build software. Don't listen to the vibe coders. They have no idea what they are talking about. Listen to actual software engineers. Take time to learn and understand what you are doing, and why. It may feel like the slow route, but you will absolutely trounce the hobbyists.

1

u/Lightlefou410 2h ago

Alors prend une formation ! N'utilise pas le vinecoding pour apprendre ou alors essais de comprendre chaque ligne que l'ai écrit !

Selon moi le best c'est de prendre une petit formation dans un langage pour avoir les bases !

1

u/Blixblix07 29m ago

Ca me donne l'impression de pas être optimal en temps passé de faire comme ça

1

u/abateslop 2h ago

The fact is you won't learn unless you do. Reading a Harry Potter book doesn't make you an author. You either need to brainwash yourself by reading 1000x the book, or do writing exercises so your brain slows down to absorb the content.

1

u/ItsFlybye 36m ago

Instead of tutorials, I think one of the best ways to learn is think of something small and fun to you that you want to accomplish for the AI to do. Small website, tiny app that calculates something silly, etc. Have it explain the different concepts. Then try coding it yourself. This way the early learning process feels like something fun on a topic you like.

1

u/arty1983 19m ago

You can learn how to hammer nails after using a nail gun for a day I suppose, nothing stopping you

0

u/Zelderian 9h ago

Honestly, ask it to make you a beginner “learner” website, then have it built a lesson guide on it to help explain different aspects. The great thing is you can have it go more in-depth on the parts you don’t understand, and skip over the parts you do.

You can learn from reading formal books or watching YouTube videos, but tbh I feel like you can experiment with it enough to learn practical applications of it. I’ve certainly learned a ton about CI/CD pipelines and Git thanks for vibe coding.

0

u/HappyTopHatMan 9h ago

Learn to read it. Know how it will execute without using AI or your debugger. Challenge yourself to create specific parts or components by hand and try not to use google or other tools (that said, use google and read as many documents as you need).
You have to understand the underlying patterns and scale up from there (if, for, for each, asyc vs sync, how the code handles different parameters).
End of the day….RTFM.

0

u/CodosRS 6h ago

If you're willing to take the time to actually collaborate with ai you will learn a lot along the way! and it's definitely worth doing because you end up with better end products when implementing a more iterative and collaborative approach to development with AI

0

u/RemarkableWish2508 6h ago

If you like visual stuff, try this:

  • Set theory (practice with Venn diagrams)
  • Code flow charts (draw some simple code)
  • Propositional logic
  • Data structures (do at least a few of them)
  • Design Patterns (again, try some)

You can ask the AI to help you convert stuff into a cute drawing, it's reasonably good at doing it with simple stuff. Once you get a hang of it, learning to code is just like learning any language: learn a word/sentence, practice, keep a dictionary close by.

0

u/Next_Ambition8751 3h ago

tell claude to add short comments above every block of code explaining why it chose that approach.

also try breaking a random variable on purpose just to trace how the error ripples through the files.

breaking stuff teaches you way faster than reading definitions