Is Java EE just for the really brainy?

Question

Java

2 course. It's time to decide on a future specialization in programming.
I don't have a super analytical mind. By this criterion, I am slightly above average (when I compare myself with the rest). HOWEVER, I LOVE programming (whatever it is). Purely for myself (for pleasure and development), I write the usual desktop applications: board games, alarm clocks, a graph. editors, etc. whatever you want in short.
If you look at the statistics, you can see that java (especially EE) is the most in demand. Actually, I was interested in this direction at the beginning. I read Schildt, I keep Horstmann at my side, I solved problems, wrote a couple of toys - it went fine. Although this is only SE after all.
But the more I read articles, reviews, notes of other people about Java Enterprise, the more I began to understand that not all beginners whose eyes light up at the sight of Java at first reach the end of the Java EE / SE Developer path. For some, I will quote: "burnout" in the middle of the road and they change their specialization.
Actually, that's why I had an idea: maybe in order to reach a professional level in Java development in the future, one must be "especially heady" in advance? If so, then I hardly fit this caste (I have a couple of brainy people in my acquaintances, with whom I can compare). And this is not self-criticism, just an objective analysis of their abilities.
Are there any experienced people who can compare this direction (Java EE) with others? What do you think about this? Maybe this is all nonsense of a beginner, and I just need a good kick in the ass?))
PS: I also think to try to look towards Android development or weba in general (js, php, etc.). There konesh, too, all Pts and Pts is not easy. But as I understand it, the entry threshold (if such exists at all) will be lower.

Answer 1

Quoting you "this is all beginner's nonsense, and I just need a good kick in the ass." Take it and start doing. You need to learn immediately by practice in any language and technology. In the beginning, you can not go headlong into pure Java EE - read the theory, understand how it works, look at and repeat simple examples. And then take either Spring Boot or Play (I don’t know much about it personally) and write an application on it. Along the way, you will join the ecosystem. You will look for answers to questions and understand in practice. Yes, this is not quite a true path, because you may not fully understand how everything is inside and you will perceive a lot as magic, but you will already receive results and see the fruits of your labors. Having created a simple application, delve deeper as it becomes more complex. As a result, you will see that most of the code, which exactly you wrote the usual Java SE. Spring will do everything for you, and you just direct it in the direction you need, sometimes inserting your own implementations and configs. The devil is not as scary as he is painted. It will be cool to find an internship or a job. There they will also help you, and they will give you combat training tasks, and then combat ones.
Yes, you need to know and be able to do a little more to start writing Java Enterprise than web applications in js, php. But, IMHO, I personally enjoy writing Java more than js or other scripting languages. And besides, you still have to study js - the client part in your training projects will not be written by anyone for you).
You yourself need to try and understand which language you get more pleasure from.

Answer 2

But the more I read articles, reviews, notes of other people about Java Enterprise, the more I began to understand that not all beginners whose eyes light up at the sight of Java at first reach the end of the Java EE / SE Developer path. For some, I will quote: "burnout" in the middle of the road and they change their specialization.

Stop reading these other people and just do it.
You will succeed.

Answer 3

Just a week ago, I had the same question with the same initial data: I need to harness myself to Java EE if we move further in Java, and there are not so few brains, just not enough for all these endless frameworks. One employer needs this, another that. Well, yes, Spring is the most popular, but the very concept of Enterprise != Spring, of course. In short, I came to the conclusion that the Androida ecosystem with its quite visible set of technologies is more suitable for me. Yes, for different tasks you need to use third-party libraries in one way or another, study them, but these are not pancake frameworks of 500 textbook pages. Personally, my experience and conclusions, I do not impose on anyone.