Narrow vs Widely Focused Developer?

Question

IT education

I am a 2nd year student. And almost all my free time, about 6-7 hours, every day (6 days out of 7) I try to study Computer Science. I googled and made a plan for myself from books, and I’m already looking for books in Google, where I don’t understand.
- The code. The secret language of computer science
- Computer architecture. Tanenbaum ( now at this stage )
- SICP(MIT)
- Mathematics for Computer Science
- Algorithms and data structures. Skiena or Sedgwick
- Operating systems. Tanenbaum
- Networks. Tanenbaum
- Databases
- Compilers. Probably the book of the Dragon.
So far, almost 90 percent is theory, that is, you won’t practice much in Architecture. But I plan to study mathematics and algorithms both in theory and in practice.
I want to not just code, but to understand the structure from the inside, or at least imagine how it works. Know the foundation on which everything is built. When I start doing more applied things like Android, I immediately think that until I find out how everything works, I don’t have the right to do something)
But when I look at vacancies, it’s basically required, the one who taught what some framework and knows how to use it. And then the opposite thoughts immediately come, about my plan ((
What should I do?
UPD: I know the programming language Java. I can write simple applications on Android. But I decided to return to the basics of everything, because I missed a lot at the beginning of training.

Answer 1

A narrowly focused developer is a person who thoroughly knows the nuances of his niche and has a lot of experience in the issues that arise in them.
A broadly focused developer is a person who has tried many things and successfully implemented projects in several different niches.
And the one who lay sideways, leafing through Tannenbaum and Dijkstra, is not a developer at all, and no one will hire him for the simple reason that he has no experience, and no one will pay for the time while he will gain it, stuffing his noob bumps didn't run away.
Books are wonderful. But in developers, they value not the ability to pass tests, but real experience and acquired skills. Even if the HR idiots are hiring against that logic.

Answer 2

about 6-7 hours, every day (6 days out of 7) I try to study

Approximately 60% of this time you are wasting.
The rest is some suffering and keeping up to date.
And how did you want? Would you take a programmer who knows well the theory divorced from practice, but cannot write normal code? No, they didn’t, you will take a code slip, which once and again and into production.
So stop talking and go ahead, smoke frameworks and go to the factory, waving clowning around.

Answer 3

The list is objectively weak. After this, they won’t even take you as a junior. Be sure to add the following:
"The Art of Programming" by Knuth (of course, all 4 volumes)
"Techniques of object-oriented design. Design patterns" Bows of Four
"DDD" by Evans
After that, you can try to go to social security for an intern
PS I really hope that your question - it's trolling