Literature, about how to read books?

Question

Python

Hello everyone! My name is Victor, I am a student. I study to be a programmer and do programming. I had experience working in companies, developing websites and applications. But each of them said to come later... they say it's worth learning... I studied programming from video tutorials. Now I realized that it’s better not to do this, since it doesn’t wake up a general understanding of the structure of the language, in general, understand the language in fragments.
Now I decided to study programming only from books. Everything is fine, only one problem worries, maybe you can help, figure it out. And the essence of it is this: when I read a book, I first read the chapter, for example, I look at how the code works, etc. Then I type in the code. And then I reread it again, because there is a fear of missing something important. What is the problem? When I read it again, I lose 20-30 minutes, when at the first reading I spend 5 minutes on everything. In general, it takes a lot of time, therefore the book is read very slowly and boringly. Should I read it a second time? Or if I read it once, understood the code, typed it, should I just move on? And besides, I was told that I have a pretty poor understanding of the application architecture, then I should read books about algorithms?) Thank you)

Answer 1

When I study from a book, I first try to read everything that I consider necessary at the moment. Then abruptly I begin to do what I started reading this book for. If something is not clear or a new task has appeared, I turn to the book again and so on in a circle until I do what I want).
Example, I want to make a lab on cycles in C ++. I read the section of the book about cycles, I read it. I'm starting to do a lab, something is not clear what the hell with the for loop, I look in the book. It turns out that arrays are needed, I read about arrays, I do, I have a problem, I read, I do, and so on until ready.
I believe that the advantage of this approach is that in one reading you get a lot of information about important and not so important. Of course, you are not able to assimilate and understand it so quickly, but when you try to do something, you have a more or less general picture of everything that happens in your head and, if necessary, you know where to turn for the details of this picture ...
You can count everything this is nonsense, but it really helped me when I was just starting out and didn’t know what to grab onto. Now everything is easier, I know what I want and just google it).

Answer 2

In general, it seems right to start learning a language from a book, but it doesn’t work very well. A lot of good new knowledge is mixed up, the concepts of different levels overlap and in practice you still do it wrong.
I advise you to start learning the language by writing code. There are many good online resources where you can do tasks in the browser, such as Codecademy.
Or solve your cases, at least on a stackover flow, but start writing. Then, when you read the book, you will see not a flurry of new information, but a deeper understanding of what you already know and correcting your mistakes.
This is how I taught Python, first I took a course at Codecademy, then I found a part-time job remotely, and now I’m reading Lutz. And this is exactly the feeling when I understand what it is about, but I learn the subtleties and improve my style.

Answer 3

In general, on the example of Lutz's book www.books.ru/books/izuchaem-python-4-e-izdanie-816...
It says how to read this book and at the end gives a checklist of questions, if you could not answer, then you need more re-read or read more slowly and carefully the first time.
Then do not go in cycles, this is a book. Read on. When you've read the entire book, put it down and read it again.
Then you can put it aside and read it again. You are not preparing for an exam, and cramming to become another Indian programmer is clearly not a very good way.

Answer 4

Perhaps you should not study aimlessly? Can I program something specific, and not display hello world 50 times in a loop?