Thanks for writing this book. Algorithms are one of my favourite areas of exploration. Looking forward to read your book.
I have a couple of questions:
1. Usually, books on algorithm design focus on the well known data structures. How do we extrapolate and apply this knowledge to more complex data models that one encounters in real life?
2. Given that algorithm design has been an essential part of academics, but as one completes academics and moves ahead in the career, this knowledge and skill usually tends to be used less. How can one find ways to keep exploring and exercising the algorithmic-thinking muscle?
1. That's a tough question. I don't know the ultimate answer... but for now, I think that books like mine can help train the reader on how to recognize when a data structure is needed. Maybe my book doesn't contain the specific data structure that they need, but hopefully with the background from the book they now know how to find it.
2. I agree! Sometimes we can get locked into a particular area of programming and lose the fundamentals. I don't know if this would be fun for you or others reading, but I really enjoy solving programming puzzles from programming competitions. I'm way too slow to actually compete, but I can compete with myself these puzzles were a major motivator for me to write this book. I've kept writing about new puzzles/exercises to supplement the material in the book... you can check it out if you like:
Thanks, CodeRanch, for talking with me about my algorithms book! www.danielzingaro.com/alg
I also enjoy solving challenges, though I am not up to hard challenges yet. I joined Advent of Code last year for the first time. The first ten days were fine, but after that my wheels started falling off. It was there that I particularly wished I knew more about algorithms .
They worship nothing. They say it's because nothing is worth fighting for. Like this tiny ad: