I don't think that books are good place to start (because they are usually long and outdated), but if you are book-person I can suggest you the following ones:
Lessons Learned in Software Testing: A Context-Driven Approach
How Google Tests Software by James Whittaker
I am a big fan of cheat sheets. For example, I have printed chet sheets about Vim, Docker and Git on my desk. For example, ZeroTurnAround has a lot of beautiful cheat sheets. Or you can find them in Google. Or you can do them yourself. The point is – don't try to remember everything by heart.
Learn to google. I mean, not just ask your question Google first and only then your collegue, but learn it's syntax. For example, do you know what quotation marks actually do in your search request? Or how to find something only on Estonian (or whatever language you want) site? You can find some infographics like this about Google's syntax – it will save you a lot of time not only in testing.
Command line is a friend of every professional computer user (even a librarian). After all, computer is only a tool that helps you to do your work. And command line is very useful option of this tool.
Vim – as for me, it's very powerfull staff, so you must know it. I used it a lot even if a were a manual front-end tester (because some times you still need to do some staff on server side where you don't have any graphical interface). FreeCodeCamp has a good article for starters: Vim isn’t that scary. Here are 5 free resources you can use to learn it.
You can also check out some of my blog posts about command line staff:
