How to read technical books? So many concepts to remember
Do you keep notes on the way? I meant books like designing data intensive applications, design patterns etc. Taking notes means I would have to be at my table whenever I read. I generally read during commute, on bed etc. this is so painful...
It’s tough. I’ve found what works best for me is to read things slowly and make sure I conceptually understand everything I’m reading. Books will usually reference things that were mentioned in previous sections and I’ll either go back to that section or know that I’m solid on such things. This usually will let me recall more information when a topic comes up again in a different context. Interestingly, this is the way I prepared for algorithm interviews by making sure I understood the fundamental algorithms very well rather than grind leetcode.
And I will caveat this by mentioning I’ve always disliked taking notes and have avoided it since high school
I’m reading data intensive applications. I think its important to go slow in this book. So many important topics are described in the book that I feel like you need to do your own reaearch about them in addition to whats in the book. I found referring to the research papers at end of each chapter very useful. I don’t read all of them but the few very important topics that should be understood in depth. I would love to know how others have approached learning from this book
Too many things to remember if you are not an expert on that ...
Idk, how did you do it in school? These books are good for reference. The knowledge won’t stick unless applied. Either brush up and cram or reference when relevant. Not cover to cover
Read a little and apply in a POC implementation later that day. Enter some bullet points into your phone to capture the train of thought as you are digesting new material. Read again if you didn’t understand the subject on the first try. If you don’t apply the techniques in practice they won’t stick, so POC implementation is key.
Take notes as you read. Good notes that can be used standalone half a year after you're done. Writing things down reinforces them, and later you can go back to it too. It will slow you down, but worth it (In addition to practice)
Create flashcards for concepts you want to remember and review them periodically.
Can you create a distributed system locally ..I am facing the same issue..no talks about scalability and distribution at work
Virtual machines, or, a pile of Raspberry Pi
Cracking coding interview and programming interviews exposed should be good enough
I meant books like designing data intensive applications, design patterns etc.
Lynda has a good tutorial on design patterns and for design either books or YouTube video