this post was submitted on 13 Oct 2023
12 points (92.9% liked)
Programming
17694 readers
178 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Don't rely too much on chatgpt before you understand the basic concept.
You should also read the books. E.g. pick axe book(i.e. programming with ruby). You could also find the recommended books in your CS50 course. Also ask your online course buddies and instructors for help.
If you only have exp in html, css and js, don't regard yourself as you are already familiar with programming. Learn as a beginner. Go back to the earliest topics you have trouble with. Try to get the concept and work your ways to the situation where you feel overwhelmed.
Good luck!
I personally disagree with this massively. ChatGPT is really good at explaining concepts.
Don't ask it to write your code though.
The problem is, ChatGPT tends to be very willing to throw code at you, even if you didn't ask for it.
LLMs aren’t going to give you a roadmap or prioritize concepts. They also frequently produce contradictory information.
They’re good tools if you already have some experience and vocabulary in the field, but a more structured approach to building some projects and acquiring skills is better.
Indeed. But you just have to learn to use them like any tool.
Most things that used to be a Google followed by skimming articles can now be a question to them.
They are also remarkably good at explaining code snippets. If you drop a line of code in there and ask it what it is it'll explain it piece by piece with correct terminology and answer any follow up questions really well.
That gets around the not knowing terminology problem that many beginners have
I do this frequently with the legacy SQL I have to deal with at work. It can handle some really nasty stuff very well.
If I go over existing code then it all seems to make sense. And when I start coding I can recall the relevant code from the lectures, notes and previous exercises. But I often get stuck on using the right syntax when working with new concepts. Then I prompt that part like a debugger, and ask it to explain how and why it works; so I can proceed. I haven't check any of the recommended books so i'll dive into those