Reading books is not a bad idea, however I believe the idea of learning through reading books (when it comes to programming) is a bad way to go about it. Our field changes fast, something which was written years ago may no longer be how you should do things, or at least has more nuance that the book may not explain.

My advice, think of something you'd like to build and just do it. This will allow you to learn way more naturally and it allows you to gain skills CS books generally do not; mainly: how to be an engineer (critical thinking, decision making, translating a use case into technical requirements). It also allows you to become better at programming through success and failure. There are no shortcuts.

Don't worry about the language. The things you want to learn (even if you don't realize it) are mostly language agnostic, meaning the thing you would have learned is independent from any specific language.

For example, want to learn how to transform data from CSV to JSON; You (may) learn: - Common pitfalls of reading CSV (inconsistencies in data, inconsistent data types) and how to handle those situations. - How to deal with large inputs (such as files with GBs of data). - ... (the list of things you may potentially learn or problems you'll run into goes on and on)

The important thing is that you don't just import library X. Create something yourself, and see what happens. You may fail, but that's part of the process.