Front Matter -- I What the Beginner Needs to Learn at Once -- II Relating Chiefly to Engineering Managers -- III Purely Personal Considerations for Engineers -- Back Matter.
https://www.asme.org/publications-submissions/books/find-boo...
It's a bit dated but has a lot of helpful advice - I wish I had read it when I started my career.
They're excellent books, but they're targeted for early career developers and people struggling to figure out the office work life. It's fair to say that you're probably not the target audience, but they're really great books for their niche.
I'm also extremely interested in the idea of reading a book about remote work after reading the blog.
Maybe it's not Remote, but I should definitely read a book about working remotely, considering I do it for so much of my time.
I was fortunate enough to be around senior engineers who took upon themselves to mentor junior engineers like myself. Now that I'm in their shoes, I find that the engineering landscape has changed quite a lot (especially in software) and often find that junior engineers don't see themselves needing to be mentored and sometimes even offended by recommendations.
I think some of this can be seen in this thread as well - some are commenting about how bad these recommendations are, and some even about the general practice of recommending books (how dare you!).
Given that the OP is just talking about books that he felt changed "his" career, I think it's really not something to be challenged and disagreed in such manners.