How do you use AI without letting it do the learning for you?

Hi everyone — I’m interested in hearing how people here are thinking about AI tools while learning to code.

There’s a lot of advice online about using AI for programming, but I’m especially curious about the learning side of it. When you’re working through lessons, projects, or debugging exercises, where do you personally draw the line between getting useful help and letting the tool do too much?

A few questions I’d love to hear thoughts on:

- Do you use AI while working through freeCodeCamp lessons, or only after you’ve tried solving something yourself?

- What kinds of prompts help you get unstuck without giving away the whole answer?

- How do you tell whether you actually understand a solution versus just recognizing that it works?

- Are there moments where AI has slowed down your learning or made you less confident?

- Are there ways AI has made learning more approachable for you?

I’m not looking for a single “right” answer — just interested in how other learners are handling this balance in practice.

What has worked well for you, and what would you warn beginners to avoid?

No. I post on the discord and get humans to help me.

(unless I need help with a repetetive task like creating false data for a test or something annoying like that, then AI can help)

I think some researchers tried to setup an AI with prompts to stop it giving away the answer and they said that it still gave the answer a good percentage of the time (I can try to find the resource if you want to see it)

So - I would say - no specific prompts will really stop the AI from being too helpful.

I can tell i understand it cause I wrote it myself.

Yes. I’ve tried to use AI to help me resolve issues with git. And because it usually helps me, I am not really any good myself and git debugging/problem-solving.

Not really. But it does enable me when I don’t feel like asking a real person a question. So it has made it easier for me to pretend I know stuff.

It just hasn’t worked for me in terms of learning at all. I’ve used it with technical issues I do not care to learn though.

If you actually want to build self-efficacy don’t use ai . That defeats the purpose

Welcome to the forum @nb_fcc_forum_1

AI has certain use cases.

For learning though, AI can sometimes confidently give misleading information.

Think of it as a tool. You’ll learn more using hand tools first, rather than jumping straight to power tools. When you are experienced enough, using power tools / AI can let you do things faster / better and the learning curve isn’t that great. With a solid foundation, you can tell when AI makes mistakes and take corrective action.

Plus, in the real world you’ll need to communicate with people; discuss bugs with other developers, talk about design and requirements with customers and end-users.

There’s already IDEs and linters that make coding easier. If you don’t spent time coding / debugging then you could potentially limit how much information you can retain. The frustration that people feel is the process of making synaptic connections in the brain.

When you’ve learnt the basics, built and deployed some projects, can explain the code you wrote to a potential recruiter, then that’s a good time to explore AI tools.

One of the quotes on the freeCodeCamp website is:

“There are no shortcuts to any place worth going.”

- Beverly Sills

So for a beginner, do not rely too much on AI for your learning. Exploring a little is fine.

Happy coding

2 Likes

I have been viewing AI as a form of automation that automates aspects of my work to improve how much I can get done at a given time. I have been using an aviation analogy lately and this applies here. You can learn to fly with the autopilot, but you must know how to fly the plane by hand, along with knowing how the autopilot works. It can help offload workload from you, and do this more accurately, but you must know what it is doing or you will get into trouble.

Learning with it is a little more of a mixed bag because it can easily get things wrong, and provide the wrong “output” if your “input” isn’t correct. There’s some ways to utilize it, such as finding information in a more streamlined fashion than say just searching it. But you really need to have that muscle to bypass the AI and search things yourself, otherwise you end up beholden to whatever the AI gives you with no skills to find anything else out yourself.

- Do you use AI while working through freeCodeCamp lessons, or only after you’ve tried solving something yourself?

- What kinds of prompts help you get unstuck without giving away the whole answer?

I’d entirely bypass AI until I build the muscle memory, or ability to identify and reference existing/external material. AI can make me faster here, but again I want to build that muscle, not rely on AI to be that muscle.

Later when I need to go faster (like on a larger project) where I might roughly know what I need, but don’t want to manually go find it, I ask AI to synthesize the answer with my information.

The frame of mind to know you “know” the answer is you know what the AI writes before it writes it. If you are even slightly surprised or unsure of what the AI wrote, you should stop and look into what it is doing and why. It could just as easily be doing the wrong thing.

Another comparison I make is AI is like a calculator, both are computation machines that you can use to make your life easier.

Depending on what you are learning having a calculator can either help you solve the problem in a sensible time as it automates the nitty gritty details. Or it can just outright give you the answer.

AI can and will just give you the answer, which is why you don’t get a calculator in early math classes at all, you have to do things slowly and manually. Having a calculator here doesn’t “help you learn” it actively makes it harder as an easy way out.

Where someone is in their journey and how they can leverage AI makes things more difficult in my opinion. Its ultimately a useful tool, but an even better crutch that is always ready to give you an answer (maybe not the best one, or even the right one) which makes it tantalizing to use.

2 Likes

100% this :up_arrow: :up_arrow: :up_arrow:

1 Like

Let me start by saying that its HARD to make it assist you learn in a good manner. I use AI to assist me learn new things all the time, but it always takes a couple of prompts to mold it into the assistance I need, and even then it gets to overstep ones in a while. I’ve tried adding instructions and whatnot, but nothing is sufficient. Keep in mind I do not use the most expensive models, so that might be part of it.

What I’m currently learning nowadays for example is to build an app using said and said technologies, incorporating certain libraries etc. My tactic is to make AI act sort of as a freeCodeCamp curriculum, splitting things into small tasks and going step by step. Usually I would use it to devise a larger working plan. One big issue AI tends to lean on is to leave a lot of specific guidance, which later it follows silently, yet that guidance might be wrong assumption at that time. So its important to always make it doubt and elaborate when making decisions, or providing solutions, and also not leave too much preemptive guidance, until the point to implement something comes by.

Another major struggle is to make it build at the right pace. It would either spit a large successions of steps, or it would feed you small spoons, so it usually takes a few prompts per session to get in the right pace.

When we talk agents, they always tend to rush to implement things and would take hint for assistance as a nudge to write code, another thing that needs to be overwritten and established per session.

As someone that has some experience, I do have my own opinion and vision how to do things, and I use AI to lay down the options in front of me, for me to question them and come (on my own accord) to the right solution and then implement it. Sometimes I ask it to provide me only the steps, do this and that, and I implement it, but most of the time id also request for code snippets simply because it becomes a redundant task to write the same functionality over and over. I still follow the snippet and write on my own, just to follow the logic and eventually doubt it, or tweak it, in order to understand whats going on.

Now keep in mind this learning strategy is totally adapted to my needs, and might not fit for someone who is learning recursion, or goes through the actual fCC curriculum, or needs to focus more on coming up with complete and thorough solutions on their own. In that latter case, id use AI more for asking more local and specific questions, that commonly come when you doubt something which is not explicitly told in the curriculum lesson.

I could go on with tips and my own learning experience though AI, but this already becomes too long

Looking up the history of Ai.

Hi,

I’m new here, so mine is a fresh perspective/approach to your questions. I’ve been using AI coding tools for a few months. I don’t have a background or qualification related to code so this was quite a steep learning curb. You’ve got some interesting questions and I really want to share my journey.

I use about 4-6 LLMs for coding. I’ve got a rule in my AGENTS.md file stating that all LLMs need to speak simply - no dev talk. This helps me understand what’s working and what’s wrong both of which help me understand or learn about what I need to do to fix the problem.

I’m a noob and keep a folder full of stuff I’ll forget. Things like instructions for running technical or operational debt audits for backends and frontends.

I guess this depends on the project I’m creating or the problem I’m solving.

Quite the opposite. This was never my strong suite, although the use of these tools have added to my knowledge.

Yes. There’s no bad AI, only bad users. I find that if I articulate very well my problem or what I’m feeling about something I don’t know, then AI does a decent job at identifying my bottleneck and offering a list of solutions.

Understand the strengths and weaknesses for all LLMs. Like Codex is great at architecture and scaffolding, and Claude is great at ideating or creating. If you find that a certain ‘prompt’ or ‘instruction’ works, then save it. The most important thing for me is the saying, “If you can’t explain it to a Grade 1 child, then you don’t understand it enough” - which translates to, if you can’t be clear to an LLM about what you want, it’s almost certain that the outcome isn’t going to be the one you want.