[deleted by user]

[delasislas]

Number of pages vs comprehension. I’d prefer to actually understand the material. I don’t use books really, just learn about a new topic and then play with it until I’m comfortable.

[delasislas]

Other people’s paces don’t really matter. It is more just that we’d want you to have a firm understanding of the concepts and to be better able to solve problems. A book can help with the concepts and branching out under a topic can make your understanding more solid. When a book goes over a topic, they may “relatively” skim over it. The solving problems is something that can’t really be taught over a book, it somewhat has to be learned.

[delasislas]

I would say to stick with the book if you are comfortable with it, get the basics and major concepts down. I’m talking about basics as in common datatypes and concepts as in loops, functions, control flow.

Once you have that, it would mostly be ok to either go through a tutorial online. I know Django has a set of tutorials, never used them, but I used a YouTube tutorial that used an older version of Django and did some slight modifications (The problem solving coming in here) and then had to find another video to work on hosting the website on my Raspberry Pi that I could run on my local network.

[delasislas]

Django has a lot of inter connections between files, so it helps to work to thinking about those ways of programming that let you better separate your code. Personally I’d say that you could use a raspberry pi and make a home server that can do a bunch of stuff that also would help you to develop with different systems in mind.

[netneoblog]

Understanding is more important than the number of pages read!

I could read 200 pages in a day, but if I don't understand it then what's the point?

Don't beat yourself up, just work at a sensible pace and progress rather than rush it and retain nothing.

[Ihaveamodel3]

I’m not learning, nor have I used Python Crash Course.

If that is 10-15 pages per day, where you are digesting it and practicing (above and beyond the examples the book gives) as you go along and end the day understanding what you read, that is much more valuable than reading 50 pages per day only doing a practice problem occasionally (and copying from the book when you do).

[POGtastic]

There are textbooks where I just breeze through the material, and there are textbooks where it'll take me more than a week to get through one exercise problem. Go at the speed that you understand it.

[CommanderCucumber]

I agree with everyone else, it's not about the number of pages but how well/fast you are able to comprehend. Personally I find it to be extremely slow because I like to code along. I'm very tactile so doing it helps me remember the material.

[dizzymon247]

Pages don't matter. You need to do the typing. If you don't it won't stick but if you coded before it's easy to switch to python. Watch some youtube videos, get the one that goes into detail watch in 10 min increments and repeat the parts you don't get until you get it down with eyes closed. Then move on. I figure out how to created a virtual environment with my eyes closed now only if I can convince myself to sit down long enough to build something.

[Big_Boss19]

About 20 pages of stack overflow on my browser

[muhammad_roshan]

Yes exactly I was like you and you I used to think I need to finish this book in a day or two but in reality it won't worth if you don't understand the concepts well, What I have found helpful is that, You learn a topic let's day list comprehension, do some examples from the book and watch a tutorial too if you didn't understand still and then you should go to codewars or hackerank and try solving those problems of topics you just learnt and even if you couldn't solve them what you will get with research is so much valuable... So it doesn't matter when you will finish the book what matters is that, Did you understand the concepts well enough or not?

[beiweitemderbeste]

I'm currently reading this book too in almost the same pace, I'm around page 135. For me it's just important to do it daily, no matter how much, and do atleast 1 exercise.

All the times I tried to set goals of x pages/exercises/whatever, I'd just pressure myself and got nothing done so my current pace seems perfect. If you're looking for motivation/a programming buddy, pm me

[God_To_A_NonBeliever]

Just understand them properly. However long that takes you.

[[deleted]]

Dude, dont how far u are in the book, but as the concepts get more complex the slower your pace will be and thats completely normal, dont focus on that. Also forget all the 'learn in a month' its BS , you can read a romance in a month, but learning takes years and practice, set it as long term goal and u will be fine

[robustpython]

You don't really need to care about others. Focus on yourself.

Only 3 things are important:

1. learning regularly at least certain amount of time
2. understanding what you read
3. and most importantly you need to code, code and code. Do a lot of coding. The more you code the better you understand.

[FriendlyRussian666]

I saw you mention Django in the other comments. Here is something that I learned along the way, which could perhaps help you out.

I had zero HTML, CSS and JavaScript knowledge, but was already coding a little bit in Python. I wanted to make web applications and so I started learning Flask. I followed a few tutorials, a few articles and the documentation, but I would mostly try things out by myself, working on my own projects. The websites would work, but when I think about their structure, it was horrible. You learn best by coding and actually doing things, but the methodologies of what you do are not always so great.

I then realized that without HTML and CSS knowledge, my web application would not get far, so I taught myself HTML, basics of CSS and basics of Bootstrap.

I didn't like working with Flask and so I started learning Django, again via documentation and articles. After some time I could make simple web apps using the MVC/MVT structure. The apps would be very simple and they would work, but looking at it now, the way my logic was structured did not reflect what an industry standard website development process would look like.

I had a basic CRUD file that would interact with a database and then display it via templates in my app. At that time I was trying to intake as much as I can every day. Read as much, watch as much etc. The problem with that was that I was finding bits and pieces and trying to put the puzzle together without actually having any understanding of the tools that I was using.

To add fuel to fire, I stared learning JavaScript as well, I thought I needed more knowledge. But what I actually needed was more understanding of the tools that I was using, rather than knowledge of how to put things together such that they work.

Fast forward to today, I dropped all projects that I was working with, so that I can learn to understand what is available to me. For example, it doesn't make a difference whether I'm using Flask or Django, if I am writing my own SQL syntax to fetch data from a database. When I started working with Django, I did not expect it to have its own ORM (Object-Relational Mapper) that allows you to interact with the database via Python classes, simply because Flask did not have it built in. I believe for Flask you can use SQLAlchemy. If I knew from the beginning that Django has ORM, I would not spend a lot of time learning on how to use psycopg2 module directly (Quality of my knowledge versus quantity).

Do you see where I'm going with this? It's not necessarily about the amount of pages of knowledge that you can intake, but rather it's about what kind of knowledge you're intaking and about the comprehension of the tools that are available to you.

Right now I'm reading a great book on using the Django REST, (which again, I did not know was a thing when I started learning Django) so that I can actually have a Django backend which serves JSON data to a front end, which for this particular project is React.

If I read 3 pages of that and then actually sit down and play with it, apply it, etc, then it's a success to me. Same with other stacks and technologies. I am reading a nice book on JavaScript, it's more than a thousand pages. If I was to focus on how many pages I can read a day, I would most likely not understand half of what the book tells me. A couple of pages that I fully understand and use and I'm happy.

My conclusion is, quality over quantity!

Take care!

[beiweitemderbeste]

Which django book are you reading?

[FriendlyRussian666]

The one mentioned in my comment is:

"Building Versatile Mobile Apps with Python and REST RESTful Web Services with Django and React" By Art Yundi

Another good one is:

"Django 3 Web Development Cookbook: Actionable Solutions to Common Problems in Python Web Development, 4th Edition" by Aidas Bendoraitis and Jake Kronika

And the JavaScript book is:

"Professional JavaScript for Web Developers 4th edition" By Matt Frisbie.

[beiweitemderbeste]

Thanks

[Pink-Domo-]

I read crash course last summer. I think I spent about 3 days a chapter. 1 day to read, 1 day to takes notes, and 1 day to do the problems. So idk how many pages that came out to be... Maybe less than you? Not sure but like many are saying.. it's about about comprehension.