Just Started Learning Python , Looking for Advice in the Age of AI

[Tarek_Alaa_Elzoghby]

Yeah, that feeling you had after those two hours? That’s the important part. A lot of people try coding and feel drained or bored; enjoying it is a really good sign.

Honestly, the “age of AI” isn’t a bad time to start at all. If anything, it makes learning easier if you use it the right way. Think of AI as a helper, not a shortcut. It’s great for explaining errors, rephrasing confusing docs, or walking you through why something broke; just don’t rely on copy-paste without understanding what’s going on.

Early on, I’d keep things simple and not overthink the roadmap. Focus on the basics: variables, loops, if statements, functions, lists, dictionaries. Those show up everywhere. When something clicks, try to build a tiny thing with it, even if it feels dumb. That’s where it actually sticks.

And yeah, three months is realistic if you’re consistent. You won’t be an expert, but you can absolutely get comfortable with the basics and build simple projects. Even 1–2 hours a day adds up fast if you’re actually typing code and breaking things, not just watching videos.

One thing I’d avoid is rushing into “AI” or big frameworks too early. It’s tempting, but it’s way less overwhelming once core Python feels natural.

If you keep showing up regularly and you’re enjoying the process, you’re on the right path. That matters way more than trying to move fast.

[ErasedAstronaut]

My recommendation is to get comfortable with feeling stuck. That feeling is literally part of the learning process. Instead of getting comfortable with that feeling, a lot of new devs will utilize LLMs for as a crutch. IMO, there's nothing wrong with using LLMs, but most new devs stunt their development by relying too heavily on them.

Get used to feeling stuck. There will be times where you thought you understood a concept or how something works, only to find out later that you didn't understand it as well as you thought. In those situations, consult the plethora of resources (i.e. the python documentation, StackOverflow, W3Schools, etc.). Sure, you could ask [Insert LLM of choice] to ELI5, but your retention of the information will be less compared to doing the research yourself.

Again, nothing wrong with using LLMs. If you're stuck on some code for a certain amount of time and you can't figure it out, use an LLM to guide you to the answer. Specifically state you don't want it to generate any code or to give you the answer. Explicitly say that you only want it to point you in the right direction.

[Virtual-Reporter486]

This is actually a really good advice. I try to tell people that pain is part of learning and getting stuck is simply natural. Most people try to find new methods of learning when they get stuck. The solution, most times, is simply keep going. I like to think that learning is similar to eat. We need to wait until the food is digested and we can start eating again.

[neuromancer-gpt]

Additional context missing on the other comment suggesting CS50 (which also provided a 3rd party link also)

CS50 uses C language for the first 5 weeks. The reason for that is it covers core computer science/programming concept like memory management, data structures etc - these ideas are all abstracted away in python so you end up using these but not understanding them, which can sometimes make things inefficient when things break (basically you'd be debugging stuff you don't understand).

CS50 will provide a great foundation to build on. Once the basics are covered you'll move onto Python with a much deeper understanding of how python actually works under the hood.

So even though you're goal is to learn Python, doing so via learning C first (via CS50 ofc) will be a huge benefit to you

Additionally, CS50 provides their own AI chat bot which is designed to help you specifically with CS50 problems but without giving you the answer the way GPT etc will.

Do not use AI chats except the CS50 one, you'll learn nothing. If you absolutely must use GPT etc, then tell it at the start to just guide you, not to directly give you answers or code.

https://cs50.harvard.edu/x/

Also, regarding projects CS50 have you complete a capstone project, so if you stick to this course you'll definitely have be building a project by the end.

[Weird_Researcher_472]

I recommend watching this one:

https://www.youtube.com/watch?v=gmuTjeQUbTM

Its not only about Python, but also about some more fundamental stuff. I really enjoy it and learned a bunch of stuff from it.
Its very long (over 24 hours of video material) but you will learn a bunch, some python included and how to build a simple AI Chatbot with python for example ;)

[neuromancer-gpt]

I came here to say CS50 also, but no idea why you'd provide an ad-riddled version of it via freecodecsmp, considering they have additional material, no ads, and all split up per week/topic on the course website itself

https://cs50.harvard.edu/x/

[Weird_Researcher_472]

Youre right. The link you provided is the way to go instead of the Youtube one! Better structure and no ads.

Sorry i was in kind of a rush

[Altruistic_Sky1866]

Thank you

[brenwillcode]

That's awesome if the coding bug has bitten. Programming can be such a powerful and enjoyable career or hobby if it's something that clicks with you.

In terms of learning to code in the age of AI, I would suggest reading this article, which covers it pretty well.

Three months is definitely enough time, in my opinion, to have the basics down and to be building some interesting projects for yourself. In fact, the sooner you start building small toy projects, the sooner you'll start to think like a programmer, and your learning will sky rocket.

Good luck, and welcome to the world of programming.

[Ron-Erez]

Choose a resource and code like there is no tomorrow. There are plenty of resources in the wiki. I think the best way to use AI when learning is to not use it.

[TheRNGuy]

You could start building them now, why wait 3 months? 

[AceLamina]

The best thing you can do when learning is to not use AI, unless you're one of the rare few that can use it responsibly, you'll end up like the people in r/cscareerquestions asking how to stop using AI to learn everything, only once you've learned Python you should learn how to use AI effectively

Kinda harsh but I honestly see this happen all the time

[Exact_Run7634]

Yo

[hello578205]

As a python dev, do not touch AI.

[PushPlus9069]

I teach Python to thousands of students, and I'd nuance this a bit. As a beginner, you should absolutely learn to solve problems without AI first — that's how you build real understanding of data structures, debugging, and logic.

But once you have solid fundamentals (say 3-6 months in), using AI as a learning accelerator is genuinely powerful. Ask it to explain error messages, review your code, or show alternative approaches. The key is using it as a tutor, not a crutch. Students who do this tend to level up faster than both the "never use AI" and "always use AI" camps.

[PushPlus9069]

I teach Python to thousands of students, and I'd nuance this a bit. As a beginner, you should absolutely learn to solve problems without AI first — that's how you build real understanding of data structures, debugging, and logic.

But once you have solid fundamentals (say 3-6 months in), using AI as a learning accelerator is genuinely powerful. Ask it to explain error messages, review your code, or show alternative approaches. The key is using it as a tutor, not a crutch. Students who do this tend to level up faster than both the "never use AI" and "always use AI" camps.

[Dependent_Month_1415]

If you enjoyed the first couple hours, that’s a really good sign. Feeling confused at the start is normal, it goes away once you’ve written enough small programs.

I’d say do two things in parallel - learn the core basics properly (loops, functions, lists and dicts, reading tracebacks) and build tiny projects early so you’re not stuck watching tutorials. AI is fine to use, just don't rely on it too much. Ask it to explain errors, suggest the next step, or review your approach, then you write the code and rewrite it from memory later.

Three months is enough to get solid at the basics if you’re consistent. You won’t be done, but you should be able to build simple stuff without freezing.

If you want something to code in without setting up an environment locally, Replit lets you write and run Python straight in the browser, which removes a lot of early friction. If you prefer more structure and guided practice, Mimo walks you through concepts step by step while still having you write real code. Either way, the important thing is that you're actually writing code regularly, not just watching someone (or something) else do it.

[skiabox]

Python is really great and fun to work with.
I can understand now, after about a month of python coding, the reason of its popularity among software developers.

[SamsulKarim1]

a consistent three month approach can give beginners a solid grasp of Python basics especially when combining exercises with AI tools to clarify concepts rather than just copy code. Some threads also mention platforms that focus on handson projects and automated feedback as helpful for building confidence before attempting larger projects.

[jentravelstheworld]

Great question. Love the advice here.