How to study / outline books on programming?

Question

Books

How to study / outline books on programming?

How do you study books?

Do you write down the most important things from the book, example code, etc. somewhere?

Answer 1

I don't write. I'm just reading, experimenting with examples from the book along the way. After reading, they try to bomb a pet project using the studied technologies. If I get stuck somewhere, I re-read the relevant chapters, I climb into the official documentation, I google.

Answer 2

I use spaced repetition when learning anything. There is a cool program for this - Anki, score cards, and repeat every day. It's not cramming, it's just repetition.
I read a paragraph, highlight from it the main essence in the form of a question, and an answer. For example, a paragraph from Lutz

In theory, classes (and class instances) are
mutable objects. Like built-in types such as lists
and dictionaries, they can be modified directly by assigning
values ​​to attributes and, as with lists and dictionaries,
this means that changing a class or instance can
affect multiple references to them .

The main point to remember is that classes are mutable objects. Here, of course, you first need to know what mutable objects are.
For this paragraph, I create a card in anki, I put the following into the question
answer
And so every time you come across information unknown (or poorly known) to you.
And every day, you must open Anki, and repeat all the cards. It takes about 10-15 minutes, I do it on the subway, I used to do it strictly after lunch (when there is a strict time or event point, it's easier not to miss it).
I repeat, this is not cramming, and many will say "it is enough to understand, and it will be remembered by itself", but if this information is not used, it can be forgotten, and anki will always simulate this "use", and the information is not forgotten. Plus, you train your memory.
I also used to use Mind map for taking notes, but this is a complex topic that I haven’t been able to get used to yet, so I don’t use it anymore.

Answer 3

Personally, I do this: I study the chapter, practice, make simple notes so as not to forget the most important thing. For example, today I started to study OOP and Python classes. As a result, I have, in fact, one sheet of records, on which: the declaration of classes (parent - child) in a nutshell, the class constructor and the self argument are also in a couple of words, and a little about inheritance, polymorphism and encapsulation. Everything else is practice, practice, practice.
PS. Personally, I eat notes very briefly, and only in order not to search Google for the necessary information to quickly remember what I forgot, so the approach described above is more than suitable for me.

Answer 4

Hello.
I recently mastered Python from a book, wrote small code fragments on a given topic (well, like in books: separate functions, separate OOP, separate exception handling ...) and saved them to use later as an example. There, in files, he kept both primitive things and language techniques. All supplied with comments. The following set turned out:
Now I am writing a small client in Python - the method works. Periodically I look into these files if I forget something.

Answer 5

https://www.coursera.org/learn/learning-how-to-learn

Answer 6

Don't waste time taking notes. Learning is all about understanding and practice.

Answer 7

It is best to do this in the morning - when the head cooks better.
You sit down, read and carefully write down all the mistakes / nonsense you notice in a common notebook of 96 sheets.
When it is completely filled - consider that you have mastered programming.

Answer 8

I write out the basic syntax and basic thoughts when learning a new technology. So then it’s convenient when developing the first project to look for what you need, and not to go into the book / video again.