How to understand that a java internship is bad, and that you should leave it?

Question

Java

I got an internship in an enterprise project, at the beginning I was very happy. From the useful, I learned how big these enterprise applications are (seriously, I would not have seen it with my own eyes, I would not have believed it). Immediately pulled up maven and git But 3 months have passed, and I've been coding about 1/20 of the time. And so they basically throw requests to find out what the error is, with one stack trace, a year ago. I try not to be shy about asking questions, but waiting for someone to come up to me and explain is often quite a long time, because everyone is very busy. As a result, I am without debug and logs with sshon the command line, I "hack" the database in order to understand in which table the required field corresponding to the bean. I often spend hours in vain, just to work out the schedule, I can’t do my own business, I’m ashamed. I'm sitting stupid in this legacy, I try to analyze it somehow. This is despite the fact that I work part-time and try to combine my studies at the university.
I always feel like I'm wasting my time. Every time I think, these 9 hours could go to study, or to self-study (the same spring ). Although on the other hand I see comments like "in javacompetition is too high at the beginning, get a job wherever you can. But is this all for the sake of the “Work Experience” column on the resume? It’s just that even if I work at this pace for a year, what can I say at the next interview? Something more will be expected from me. I leave all my time remaining after study and work for self-study, but this is a maximum of 2 sometimes 3 hours. As a result, I gradually forget the java core , and the enterprise is very difficult (because I study it for an hour in the morning before work / study and an hour in the evening).
That is the question, is it worth it? Maybe it's really better to drop all this and dive into learning? Moreover, I saved up enough money to live for at least half a year without a penny (it’s hard not to lose it with such a schedule) and a salary in a hostel. So, the question does not concern either money, or the "Work Experience" column, or complexity. The question is only about time. It flows fast, and the question is, is it in the right direction?
I have been thinking about everything for a month with the thoughts “the morning is wiser than the evening”, but I have been doubting for too long. I ask for advice, because I don't have enough experience to make a decision.

Answer 1

You have unjustified requirements for the position of an intern
No one will teach you
You are lucky that the project is well-established and you are not really needed there - otherwise you would not be there anymore
You are lucky that your questions are answered
You are lucky that they approach you
Now what you need to do
0. Check three times that all the tasks that are hung up on you are resolved/closed
Further, in random order after a conversation with the one to whom you are attached as an intern
1. Approach the TL and ask if it is possible to take on bugs from the bug tracker or do you have more urgent tasks
1.1 If the go-ahead for bugs is given, start with the one pointed out or the most ancient one. If you do not understand how to fix it, it will be enough to confirm its existence. Ideally - write tests for him
2. Go to the nearest middle or better junior and ask him to sit behind him to watch how he / she writes the code
3. View the code of the commit you watched, understand and repeat it
4. When this starts to work out and you will have an understanding of what is happening - ask for pair programming
5. Talk to the middles - what you can do globally to facilitate their tasks. Draw a diagram, go through tests, etc., etc.

Answer 2

First, you need to understand that without experience it is very difficult to get a job, and getting an internship is a rare success, especially in an enterprise. Many would kill for the opportunity to take your place. Don't squander opportunities. Secondly, work is different from studying, there will never be a number of teachers in the office trying to teach you. People who could are overwhelmed with their own affairs. You have to fuss yourself. Thirdly, don't expect a magical rise to the professional level. On average, it takes about three years to grow to a developer (stop being a junior). Finally, inexperience can make it difficult to see the learning opportunities right under your nose. This is reminiscent of the Zen parables in which the master beats the student on the head with a bamboo stick for years, and the student wonders why he is not taught.

Answer 3

And so they basically throw requests to find out what the error is, with one stack trace, a year ago

Developers spend 80% of their time looking for bugs.
Well, novice developers spend 95% of their time on this.
This is fine.

Answer 4

I agree, just talk to your superiors on the topic so that I can study this as part of self-education. I think that the bosses in these enterprises of yours will be completely happy that the employee is not sitting idle, but is self-educating. At a minimum, I have always welcomed self-education, even sent me to courses, but of course they will not give responsible and interesting tasks until you are even junior and part-time.
As for working on a junior in an enterprise and with legacy code, that's the way it is - digging and fixing old bugs. But believe me, usually everything is fine with the salary. And the larger the code, the greater the payment for its correct support. Rewriting the system is long and expensive.

Answer 5

In the first year, it’s not embarrassing to change five jobs at all