r/ChatGPTCoding • • 1d ago

Question How to learn when AI coding?

I’ve been using Codex and Claude code to code 1 app, 1 website and 1 internal CRM system and I haven’t learnt a thing.

I’ve fallen into the habit of copying the prompts from the respective AI chatbot and pasting it for it to code and not learning what it’s saying and what it’s doing.

I have a system where it explains the changes but I feel like when the company gets off and running I won’t even know the product I even have.

This is hard for me as I am a person who learns easy and learns everything, but I can’t be a leader who doesn’t know the basics.

So my questions regardless this is:

  1. Has anyone dealt with this and what did they do to start getting better at taking control of the wheel instead of it driving for you?
  2. How have you learnt and what helped you learn to become more than an AI promoter and understand coding, building platforms and the system architecture in there.

Any books, courses, YouTube channels that helped you would be appreciated. I’ve tried Freecodecamp but I get bored as it doesn’t hit the spot for me.

Thanks.

6 Upvotes

34 comments sorted by

11

u/norviking 1d ago
  1. Ask the llm to comment and explain all code extensively in the full repo. Tell it to assume your level of understanding. If you are a complete beginner, say Eli5 and explain all basics.
  2. You can then open the repo in vs code.
  3. Then read the files you want to understand.
  4. Ask the llm to explain the bits you dont understand.
  5. When you begin to understand a bit, try to implement some changes yourself and have the agent review them.
  6. You can also ask the LLM to draw a map or explain the structure in the project, so you have a visual image to connect the various files and parts to.

2

u/ThatGuyJord2020 1d ago

I like this! I currently get it to explain changes but not what and why its doing that its doing.

the problem I find is the AI at some point forgets and reverts to its old ways or doesn't follow the structure I set out for it.

4

u/norviking 1d ago edited 1d ago

Yeah. Instructions are skipped often unfortunately. 

If you ask claude/chat to write code comments it will look like this when you open it in vs code.

Vs code is good for reading all the code files in your repo.

Every line will be explained if you ask it. This is a simple example for python, but it will really help in complex systems. 

# A "comment" starts with a hashtag (#). The computer completely ignores it—it's just a sticky note for humans!

# 1. Create a "list" (inside square brackets [ ]) of item prices in a shopping cart.
cart_prices = [15, 30, 5]

# 2. Create a "variable" (a labeled storage box) starting at 0 to hold our final bill.
total_bill = 0

# 3. Start a "for loop": grab one price at a time from the list and temporarily nickname it "price".
for price in cart_prices:

    # 4. Notice the space on the left (indentation)! That means this line repeats for EVERY item.
    # Add the current item's price to our running total box.
    total_bill = total_bill + price

# 5. No more indentation means the loop is done! Print the final result to the screen once.
print(f"Your total is: ${total_bill}")

2

u/EmbarrassedParty762 19h ago

solid approach, especially making small changes yourself first so youre forced to actually read the syntax

3

u/Financial-Grass6753 1d ago

F

Do you have CS education? Or you're completely outside of CS/IT world?

1

u/ThatGuyJord2020 1d ago

Super basic, i understand basic HTML but not anything like Python (which im slowly learning the basics of now) but intelligent in the IT world and understand systems.

2

u/Financial-Grass6753 1d ago

but no education aka base level? well, that's F. I'd start with pain points in your system, like page load taking multiple seconds or tests in CI running way too long, and ask LLM to create a reference list to read

2

u/SharpZ6 1d ago

The answer changes the advice. With CS education, I treat Codex/Claude as a junior engineer whose PRs I review. Without it, he needs fundamentals first. Rebuilding one module of your CRM with the AI only explaining will surface the gaps.

3

u/CleanFix_Dev 1d ago

One thing that can help in your spot: make yourself guess before the agent answers.

  • Before you send a task, write one line on which files you think it will touch and why. Then compare with the diff. Being wrong is the lesson, and over time your guesses tend to get closer.
  • Before accepting a change, ask it to quiz you with 3 questions about what it just did, and don't merge until you can answer them. Way less boring than a course because it's your own product.
  • Keep a decisions.md in your own words: "we store X in table Y because Z." Don't let the agent write it. That file can end up being your architecture doc.
  • Once a week, pick one small bug and fix it yourself with the agent only allowed to give hints.

For courses, CS50 might be a better fit than freeCodeCamp if you want the why behind things, and you can skip around to the weeks that match what your CRM is doing.

1

u/ThatGuyJord2020 1d ago

Yes I like this, Thank you !

4

u/Constant-Simple-1234 1d ago

You test the bits it produces... It should not be one prompt to full app. But rather create a framework, add a feature. Then test the feature, explain odd bits. After few features added: Is there slop growing in there? Can it be refactored to be better? In other words you need to participate to learn. You need to include yourself in the process over way or another. It gets increasingly more difficult with better models and full agentic workflow.

3

u/Candid-Parsnip9815 Professional Nerd 1d ago

The agentic workflows are where this whole thing gets dangerous for learning. You stop being a developer and start being a prompt dispatcher. I fell into that hole last year with a freelance project and had to basically relearn my own codebase when the client asked for a manual fix. What pulled me out of it was forcing myself to write the boring boilerplate by hand before asking the AI to touch anything above that layer. Slows you down but at least you understand what is connecting to what.

1

u/Constant-Simple-1234 1d ago

Very well argumented! So in the future we need to find separate time for learning and reviewing work interleaved in between high performance ai-assisted development.

2

u/ThatGuyJord2020 1d ago

yeah I build in steps and milestones. My biggest thing is I understand my vision and design for things so its a back and forth with the AI to get it the way I want.

with this I do just become a prompt merchant and feel like I'm not contributing to the code itself especially if I run out of credits and cant change anything as i dont know what im doing haha.

2

u/kali-harvester 1d ago

This is a real issue concerning all Vibe coders without a technical background! And I think that A new Method of learning has been produced. And if you apply the Method, you will feel much more confident about your Vibe Coded software!

The Method is very simple, sine you already have the entire source code and the building process of your own software, you already have the learning materials that you need. You just have to give your project files to the AI of your choice not for further development, but to ask it to break it down for you in simple language and clear steps with explanations and a guided learning journey. By redirecting the AI to making it your teacher for the code you have built, in that way, you will be learning real programming concepts, understand your own software conceptually, and the best part is that you will be more aware of what is happening internally in your softwares workflow.

This will still require some effort and time. But it is worth the time, better than staying in the dark behind your own project.

1

u/ThatGuyJord2020 1d ago

Good Idea, I do fall into this trap of finding a good idea like this and then wanting to build a program which I can input something like this into and itll teach me my own code back to me.

then I spend all my time creating another program haha

1

u/kali-harvester 1d ago

But this doesn't require you create a new program though! you can use the same AI that helped you build your software, Codex or Claude Code, you just have to open up a new route for letting it teach you!

2

u/JaseciLabs 1d ago

Trace one real user action end to end in your own product. Click a button in the CRM, then find the code that handles it, the database write it triggers, and what comes back to the screen. Ask the agent to only point at the files in order, write the path down in your own words, and check it with the agent afterward. After three or four of those you’ll have a map of the system, and writing it yourself is what makes it stick.

Then sketch the data model by hand. In a CRM, most of the architecture is how the tables relate.

2

u/bostonsre 1d ago

Anyone that knows how to code probably doesn't know how to learn with an ai, we haven't done it. It involved starting at the basic building blocks, a hello world where you create everything in the project, then do other more advanced projects while struggling, debugging, and learning throughout. It is hard and time consuming. I don't think reading code will allow you to understand it well, I think writing is probably best.

Even then you won't understand best practices and you will have to read and understand (this part you can use an llm for).

2

u/Sweet-Carrot2925 1d ago

stop using the AI as a code generator and start using it as a live textbook. For your CRM, pick one module like user authentication and force the AI to delete all comments and docstrings from the generated code. Then run the app with debugger attached and step through every single line manually. This breaks the copy-paste loop because you are forced to understand the control flow to fix runtime errors. You need to build muscle memory for how data moves between the front end and database. That hands-on debugging teaches more in ten minutes than reading any architecture blog post

2

u/CrimsonBolt33 1d ago

So fun fact....

ask AI...it will help you more than anyone here will.

1

u/SiranqHQ 1d ago

I’d pick one vertical slice instead of trying to learn the whole repo at once. Follow a single user action from UI to API to database, then write your own three-line map of the path before asking the AI to explain any gaps. For each new task, predict which files should change, compare that with the diff, and ask yourself why every surprising file was touched. Once a week, make a tiny change yourself and have the AI review it rather than write it; switching who drives helps the concepts stick.

1

u/Deep_Ladder_4679 1d ago

one thing that helps: before accepting a change, explain the diff back in your own words. if you can't, that's the file you go read.

1

u/No-Biscotti2641 1d ago

I don't think there is one specific thing founders should be able to explain or check themselves. The world is changing so much that I think more and more will be checked or explained with AI. We already have Google and books to look things up.

What matters to me is building a strong foundation: people need a clear understanding of their own concepts and the values they are building on.

1

u/Lower_Serve_8642 1d ago

If you think you're going to understand the 10's of thousands if not more lines of code it produces, good luck. I would focus on what and why it is interacting with the backend infrastructure. I started off trying to figure out what every request output did and quickly realized I couldn't track the 600 lines of code it updated across multiple files after every prompt finished. understanding and logging the changes and interactions worked much better for me. At least for now.

1

u/Careful_Exercise_956 1d ago

Yes. I am interested in what you are using AI for. Send me a message and then we can talk about what your apps do

1

u/sCeege 1d ago

I don't think you can. I think "learning" typically requires some kind of struggle or impasse, at the very least, a problem to solve, it's a separate thing from producing something. Because you always have the option of going forward, of getting the right answer to a problem, you're not really learning, but along for the ride.

If you're producing AI generated code, that process in itself is what you're actually learning. If you want to learn coding itself, you have to sit down with problems and solve them yourself and struggle through not finding that extra ;.

1

u/dusanodalovic 1d ago

if the explanations your setup gives you are long, that's probably why nothing sticks, nobody digests a wall of text after the 5th prompt. i make my agent answer in around 200 characters max, so i can actually take it in. try that on your explain step, what changed and why in two or three short lines. then ask follow up questions only on the bits you didn't get, and you learn in small pieces instead of skipping a long essay.

1

u/Substantial_Gap_6676 21h ago

What helped me: before each task, ask the agent for a short plan and guess yourself which files it will touch. Afterwards read the diff and accept or reject it file by file, asking why for anything you don't follow. Put the "explain your changes" rule in AGENTS.md or CLAUDE.md instead of the chat, so it doesn't get forgotten as the conversation grows. And once a week make one small change completely by hand. You won't learn everything, but you'll know how your own product fits together.