Proper reading of books on programming
I have long been interested in a very important, as for me, the question - how to read books correctly? :)
At first glance - a very funny question, you say.
But think about what will be more useful:
Personally, I try as I read the chapters to type examples (all the same, the automatically typed text is useful too), and then come up with and implement my task on a given topic.
It is very interesting that you share your opinions on this topic!
Thank you very much.
At first glance - a very funny question, you say.
But think about what will be more useful:
- Reading the chapter of the book, and only then a set of examples from it and solving problems?
- Simultaneous reading of the chapter and a set / analysis of examples?
- Reading the chapter / book and only analyzing the examples visually, but inventing your own analog examples?
Personally, I try as I read the chapters to type examples (all the same, the automatically typed text is useful too), and then come up with and implement my task on a given topic.
It is very interesting that you share your opinions on this topic!
Thank you very much.
')
Source: https://habr.com/ru/post/64268/
All Articles