There is a more polished version of this book:

https://link.springer.com/book/10.1007/978-3-031-61794-2

Additionally, there is a nice set of problems that go along with the book:

https://cses.fi/problemset/

For anyone interested, I think this is book you're talking about

https://www.manning.com/books/data-oriented-programming

I think it was Ben Tilly and I think his user name is btilly. I also remember that comment you're referring too.

That's the one, thank you.

These might of interest to you:

https://link.springer.com/book/10.1007/978-3-030-43788-6

https://link.springer.com/book/10.1007/978-3-031-24228-1

https://link.springer.com/book/10.1007/978-3-030-02462-8

https://link.springer.com/book/10.1007/978-3-031-21262-8

If by "listen" you mean by "blindly listen" (by the context of your comment it seems you mean blindly listen), this is absolutely horrible advice, and I wish people would stop repeating it. Even for most slightly non-trivial problems, physicians are often wrong in either diagnosis or treatment plans. In fact I've found physicians be some of the worst debuggers/problem solvers that I've ever encountered.

Here is book on the subject:

https://www.amazon.com/Compact-Data-Structures-Practical-App...

I haven't read the book, so I can't comment on the quality.

It seems like most doctors and your average physical therapist, lack the knowledge on what can be achived with a conservative approach. Just google what knee injury Connor McDavid (Arguably the best and most dynamic player in the NHL) had, and the sucessful non-surgical rehab protocal he went through. Most of his doctors were pressuring him to go the surgical route.

Also, a related book by the same authors:

https://algorithmsbook.com/optimization/

I really like the way the handle their change log on github:https://github.com/algorithmsbooks/optimization

It's interesting just to go through their comments.

Interesting that here the typical textbook errata is called a "change log"...