Yes, every developer needs 114 pages worth of knowledge about memory.
You don't have to understand all of it but if you can't be bothered to get the gist of this maybe computers aren't for you?
Note that I'm implicitly making a distinction between people who write code and people who are explicitly developers.
Delving deep gives you fundamental knowledge of systems, sometimes there isn't time for that which in that case use the generic library that does stuff you never needed and ship the product. But in 10 years time when that needs to actually become performant code you need to know how to fix it or someone else will be paid to do it instead.
I think it's maybe nice to know how we interact with memory in software (memory allocation/deallocation, naybe how manual memory mgmt is done, something about garbage collection?), but that's about it.