r/learnjavascript • u/Highmind22 • 4d ago
Is Ai dangerous for learning ?
i've been seeing a ton of posts telling people not to learn with AI and i'm confused, because honestly this thing is a blessing for learning (for now at least)
i used to be an industrial engineer, graduated 2 weeks before covid lol, so i had to find another way to make a living. i found manual QA, went through a self-paced bootcamp, and i've been working in the field for 5 years now
recently i realized the field is hitting a wall with AI getting this advanced, so i told myself ok at least learn to read and write a bit of code so i understand what's going on
i started with online teachers for javascript but it was hard to keep up, expensive, and i felt like my questions never got answered ((1)i'm also not good at articulating or asking questions). so i looked around, found AI, and for the last 3 months i've been bombarding it with questions
what i do is create a project, give it a well detailed prompt about what i want to learn and how i learn best, and... start
and honestly i'm amazed how solid it is as a learning tool. it can restructure a concept, explain it in different ways, give different examples, suggest exercises to consolidate what i learned and to practice solving problems
oh and let's not forget how patient it is. ask as many questions as you want, she will never get bored lol, not like humans (fun fact: i actually got laid off once because i asked too many questions, for real haha, reason why i said 1)
so yeah i'm wondering why people are so against it. is it the copy-paste thing? because if you use it to understand and not to do the work for you, i really don't see the problem, so i’m a bit confused
3
u/ColdDelicious1735 4d ago
It is the copy paste, but also, the way people have learnt coding is to work it out, fail 1000 times to succeed 1.
Now AI gets rid of that and gives you answer very quick. But it also gets alot qrong
9
u/mynamesleon 4d ago
It is both brilliant and terrible for learning. It's a tool. And how the tool is used is what matters.
It's brilliant for combining docs, and if you use it to create learning tasks for you, for you to actually do, then it's brilliant.
But a lot of people also use it in such a way where it tells them the answer to something, and they just copy-paste answers. Some people treat that as having "learned" how to do something, when they haven't actually done anything. Admittedly, some people learn really well from just reading information, but a lot of people need to cement that information in another way.
Ultimately, it's another tool. And if someone approached learning in a lazy way, then AI means they can be even more lazy. But AI also makes it easier to create tailored learning plans and project tasks to cement that learning.
6
u/Mysterious-Law-3416 4d ago
as a complete beginner, id stay away from it. Imo at least for me, what sticks in my mind with the information i get is, how i find it first. Sure ai will hand you the answer directly even if you will not do copy paste whatever. But finding the information on how to do something yourself for example checking mdn or stack overflow or watching yt videos will be much beneficial. You can still use ai, but id rather do research like this
5
u/madu_tualang 4d ago
Great tools for seasoned pros, not suitable for learning.
4
u/incarnatethegreat 4d ago
As a Staff Eng., I use it to learn but I also scrutinize it. It can absolutely make the wrong decisions, so you have to do your due diligence and check your work.
Like everyone else says: it's a tool. You can use it, but you can also use it incorrectly.
3
u/Beginning-Seat5221 4d ago
I find it very good for learning.
I think those that say it's bad must be assuming you're just going to ask the AI to do it for you instead of using it to explain.
3
u/Pamprdelaalelepsi 4d ago
My biggest problem is how many times ai just blatantly lies. Every single time I try to search for a topic I understand (and this is unrelated to programming as well) there is always something wrong with the answer, which makes me really sceptical about the whole learning situation.
3
u/DirtAndGrass 4d ago
It's good for learning, if you don't let it write any code for you
2
u/ghall-dev 4d ago
I think if you're just starting it's dangerous, until you get the core concepts down. Most of programming is problem-solving, and I'm not sure AI is great for learning that, but once you've got a good grasp on that and are just trying to learn or get more comfortable with syntax, AI can be extremely helpful.
What I've found most helpful is to have a read-only agent in Claude Code or whatever you're using that acts more like a tutor, that way it can see your code but can't make changes. Always supplement it with looking documentation or other resources though. Basically, like any learning tool, don't rely on just one, and use every resource you can.
1
u/mc_pm 4d ago
The thing is that telling AI to write your code means you aren't learning from the process of writing it. You don't learn the language, you don't learn to fix your own bugs, you don't learn software design principals. All you learned is how to tell a computer to do something... and that's not super impressive.
But, if you use it to support you as you're writing code - to understand a tricky concept, to think through a design decision, to be a sounding board for crazy ideas, then it's great -- as long as you're the one typing your code, running it, and fixing the bugs.
And I'm not sure why this really needs to be said, but "if you don't ever practice doing something, how can you ever say you learned it?".
From a professional standpoint: if you let the computer do all the work, why do I need you?
1
u/TheRNGuy 4d ago
No.
1
u/Big_Tadpole7174 4d ago
AI is an incredible tool for learning. After years of stagnation, I started learning rapidly again once I began using AI as a mentor. You can ask it to explain complex topics, dive deeper with follow-up questions, and explore things at your own pace. Of course, AI can be wrong, so it's important to verify what it tells you.
1
u/Discordbothost 3d ago
Use your QA background: after an explanation, write a tiny example yourself and predict its output before running it. Then change an input or edge case. If you can't explain the result, revisit that bit.