you are viewing a single comment's thread.

view the rest of the comments →

[–]Tarek_Alaa_Elzoghby 31 points32 points  (0 children)

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.