r/PythonLearning • • 8d ago

Realistically, how long does it take to understand Python?

I am very new to coding (2 days old new) and have no background experience. I was just wondering at what point do you think you should start understanding Python? I’d like to try and create a timeline before saying ‘I can’t do it’

19 Upvotes

17 comments sorted by

8

u/Slight-Living-8098 8d ago

It's different for everyone. The first language you learn is always the hardest and takes the longest. If you practice everyday, a few months and you should have a good grasp on the basics.

1

u/Some-Passenger4219 8d ago

I started with Logo a long time ago.

6

u/FancyEveryDay 8d ago

Depends on what specifically you mean by "Understanding Python".

Learning a little bit of code takes a couple hours, learning how to design and write programs takes a couple years.

If you just want to know enough to feel competent writing scripts to automate simple repetitive tasks or call information from API's, expect between 3 and 6 months or so.

Python syntax isn't the hard part, most of what you're going to be learning is basic programming concepts like loops, functions, classes and then eventually how to turn those concepts into algorithms.

2

u/cthulhu944 8d ago

And once you learn the basic programming constructs then learning another language is just a matter of figuring out how the new language implements those constructs.

4

u/arivictor 8d ago • Bravo

Learning to program is separate from learning a language.

You know how to drive a car perhaps, but every car behaves differently, but the concepts are relatively the same.

That's how languages are. So I'd say learn programming concepts and apply them to a language and the goal is then to understand how a programming language supports what you want to do.

For example, we might have a situation where we want to do things at the same time, what's that called? Its concurrency. So we might then think, well which language supports concurrency the best, what are our requirements, what's our skillset, our tech stack? should we use Go? Python? C++?

Understanding what you need to do first is greater than needing to understand every nut and bolt of a language. If you can articulate your logic in plain english you are 80% of the way there. There is not shame in googling "how do I do X in Python" so long as you understood why you are doing X and your logic is sound.

2

u/stepback269 7d ago

Beginners tend to have Great Expectations without understanding why they are such.

As a beginner, you need to consider yourself a baby and learn to crawl (the "fundamentals") before you can stand up and walk or sprint. So search for the Python "fundamentals" on Google and/or YouTube.

With that said:

(1) There are tons and tons of tutorial materials out there on the net including many good YouTube ones that are free. You should shop around rather than putting all your eggs in one basket.

(2) As a relative noob myself, I've been logging my personal learning journey and adding to it on an almost-daily basis at a blog page called "Links for Python Noobs" (--HERE--) Any of the top listed ones on that page should be good for you. And there are many add-ons at the tail end of the page. Personally, I cut my first Python teeth with Nana's Zero to Hero (==HERE==). Since then, I've moved on to watching short lessons with Indently and Tech with Tim. You should sample at least a few until you find a lecturer that suits your style.

(3) The main piece of advice is the 80/20 rule. Spend 80% of your time writing your own code (using your own fingers and your own creativity) as opposed to copying recipes and only 20% watching the lectures. Good luck.

1

u/backend_developer89 8d ago

I don’t really know, it depends on how much effort you put into learning. You may be able to master the basics within two weeks to a month.

After finishing your course I would suggest starting easy leetcode problems, even on easy they can be significantly more difficult for a beginner, but take your time on each problem and don’t be afraid to look things up.

There’s also frameworks you can learn like Django or flask, or libraries, which will take significantly longer to learn than mastering the basics.

All in all it could take several years to master python and a framework along with several important libraries, just simply because there’s so much more to learn then just lists and for loops and such.

What I’m saying is I’ve been learning python for several years and I still don’t ever believe ‘I know python’ because I also do a lot with Django and Django specific libraries. It’s an arduous process

1

u/SympathyExciting1666 8d ago

It depends on how often you practice and how fast you grasp things.
It’s different for everyone.
But the more effort you put in, the faster you learn.
Keep practicing until it starts feeling like muscle memory.

1

u/Federal-Chicken-6788 8d ago

tbh bro it differs from person to person everyone does not have same kind of brain..... overall if you see you must have to give approximately three months to proper learn ... it includes from learning syntax to building logic for every problem by ownself ... if u are only interested in learning syntax of the python then it will take only 10 days and u will be pro in python ... so basically you have to figure out this by yourself ....

1

u/Fun_Army2398 8d ago

40 hours to learn the basic syntax, variables, conditionals, and loops. 40 hours to learn functions and libraries. 120 hours to learn the basics of OOP. 120 hours to learn the basics of relational databases. That'll be enough to do a very basic beginner project with actual usefulness.

1

u/AdDiligent1688 8d ago edited 8d ago

I’d say around 6 months you’ll understand it more, how to write it, how to read it, how to create/interpret the logic, you might understand how to comprehend documentation as well. You’ll know more about what you don’t know, but also how to address the unknown. That said, you won’t be an expert, you’ll still be a beginner, but you’ll be more capable than now. You’ll need a consistent practice and learning agenda to get there, though the strategy is iterative, and subject to change based on your evaluation of whether it’s working or not for you.

I’d suggest learn and practice as often as you can, not all doing (writing code), but a balanced mix of doing and ingesting (learning concepts), both unstructured and structured learning; both fast and slow; you’ll need to learn how to create structure from no structure, and that is one of the most difficult learning curves there is with programming, not just learning the skill in general but even within the code being able to start and make your own structured program. You will be able to do it and probably surprise yourself in the process in time with consistency and dedication.

But that is one of the first big rivers you need to cross and ultimately all these efforts will train your brain to do so. And once the creation of structure skill gets to be regular, you’ll eventually start seeing solutions ahead of time and be able to pick the best from those in order to solve the problem. Even if you’re not the one who came with it, your brain has now learned, how to identify the problem, explain the problem, use resources to solve the problem, and then integrate the solution, into the rest of your structured program you created from no structure; it was once a blank canvas, but you made it into a painting.

And the entire system of that program in and of itself is a solution of some kind. This is the first step in generalization to see how a program could fit as a smaller solution or feature in a much larger system of many solutions. Many programs can act in accordance with one another to create a massive set of solutions, that all make up, a product.

Anyway, not to get too abstract with this haha, kinda getting carried away here, my bad. But you get the picture hopefully. It starts small with learning and once you get the gest of things, you’ll be more capable in order to create solutions with programs essentially. In that sense it’s less about building the programming skills and more about building the mind in order to consider both smaller and larger windows of reference; it takes time.

1

u/468Cliothecat 8d ago

I ran aground on OOP. The more I studied it, the less sense it made.

1

u/StrayFeral 7d ago

Realistically this all depends on many things. One is how fast do you learn in general. Another is if you have a previous programming experience. Let's say you learn slow and you don't know any other coding language. Then I guess we can say if you start reading "Programming Python" or "Think Python" O'Reilly books, you should feel comfortable with the end of the book after maybe 6-8 months. These are the basics and I can say Intermediate level too.

1

u/Unable-Hawk-206 7d ago

Took me a month or two so to get decent at python but I already knew some Java and C++ at the time, also I was a student

1

u/Independent-Sound-92 6d ago

Eso es relativo hay personas con memoria fotográfica qie aprenden muy rápido pero hay otras personas que llevan 2 años y aun no entienden muy bien algunas definiciones yo diría que depende de que tanto empeño le pongas a aprender

1

u/smiggysmapp 3d ago edited 3d ago

It's hard to say. You're a total beginner, so no matter what language you start with, you're going to struggle because you're learning more than just language-specific syntax and quirks. You're also learning about all sorts of other programming principles. You're learning algorithms, strategies, design - all sorts of stuff. You're learning how to think about coding the way a programmer would. That's a lot of other work on top of having to learn the syntax and the keywords and how to handle files and errors and input and output etc etc etc.

Mark your progress in weeks and months. Not days.

It's similar to music. Learning the first instrument involves learning about a lot of music-related skills on top of learning technique specific to your chosen instrument. Picking up another instrument, especially one in the same family, isn't as difficult because there's less overhead.

EDIT: I'll tell you what I did. I used edube.org to learn the basics. Use that or any tutorial you find.

Then I started doing challenges like Advent of Code. I'd just go as far as I could for a given year. I would always try to do something on my own for a couple of days. Then, if I still couldn't solve the problem, I'd look at someone else's solution on the Advent of Code subreddit. I would go line by line to make sure I understood everything. You can learn tons of new techniques that way.

I would then try writing my own projects. Find some beginner project. Read what you're supposed to make, then try making it before looking at a solution. Whether you figure it out on your own or not, that'll make your learning stick better. Don't ever just mindlessly copy someone else's code. At the very least, you should go line by line and explain what's happening to yourself. Reading other people's code is a good skill to practice anyway.

0

u/mc_pm 8d ago

Weeks-to-months depending on you - if this comes easy to you and you work at it, you can write & read basic python in a couple weeks.

If you treat learning to program as a thing you do while watching tutorials, then it's months-to-never.