2. Skip the second half of the book when the chapters switch to being real world examples
3. Having trouble on a particular section? Watch the youtube video to get a cleaner read: https://www.youtube.com/watch?v=22hwcnXIGgk&list=PLOtl7M3yp-...
4. Don't spend too much time on NP/NP-Complete/NP-Hard topics
5. Over learn chapter 2. This is arguably the most important chapter having a deep understanding of runtime analysis helps you in every other chapter and on the interview
6. Don't spend too much time on writing proofs in Chapter 1. Understand them and be able to work through them and understand how the math comes together, but writing a specific proof isn't too valuable.
7. Sometimes the interview problems at the end of the chapter are silly. If it feels dumb, example: 1.36. How much does the ice in a hockey rink weigh? Skip it. These are older school programming interview questions and have been largely phased out