Proper reading of programming books

    I have long been interested in a very important, as for me, question - how to read books correctly? :)
    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 set \ analysis of examples?
    • Reading a chapter / book and only analyzing examples visually, but coming up with your own analogues of examples?

    Personally, I try to read examples in the course of reading the chapter (all the same, typed text is useful, too), and then come up with and implement my task on a given topic.
    It is very interesting that you would share your opinion on this topic!
    Many thanks.

    Also popular now: