Quick tips on how to use the Algorithm Design Manual 4 points by danielgh7 54 days ago | hide | past | favorite | 2 comments Ok so the high level breakdown: 1. Read and do the problems for the first half of the book. Do not rush this part of the process. 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-DX6ic0HGT0PUX_wiNmkWkXx 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 outUltimately I feel like this book is the best resource for big tech interview prep, and I want to help my students spend their time as efficiently as possible. If anyone has additional advice or feedback on how I can improve this list, I'd love to hear it.

 1. Read and do the problems for the first half of the book. Do not rush this part of the process.2. Skip the second half of the book when the chapters switch to being real world examples3. 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 topics5. 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 interview6. 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
 Nice, thanks for the advice :)

Search: