What are the team responsibilities of a .Net junior?

Question

ASP.NET

Finally got a job as a .Net junior, it was not difficult, and there were surprisingly many offers due to past experience. I chose an offer from a company where a friend works, I have been working for a month. But there is one BUT. The task area on the project is not at all related to the architecture of the system itself, neither working with ASP.NET Core, nor MVC, nor the DB, just constantly editing narrow functionality for the state customer on a kind of framework that was written by the same company. All I've learned during this time is how to work with git and with builds. Because of this, there is a feeling that there is no development at all, the tasks themselves are of the same type and it is not difficult to solve them, the difficulties are only in parsing someone else's code and in parsing the functionality of your own framework. At the same time, my curator explained that most of the tasks of this kind, but his experience and his tasks indicate that that there are still many normal tasks, as with the use of ASP.NET, the implementation of the API, the structure of the web system itself, and so on. I got a job with a great desire to constantly learn and apply something new, quickly grow as a specialist, reach a confident middle, and as a result I am engaged in stamping tasks of the same type that are not related to web development and .NET tools. The desire to develop and gain experience disappears, since there is not even a basis for this. From this question, when is a junior allowed to do normal tasks on such ready-made projects in such companies and is it allowed at all? Should I leave for another company where the scope and experience will be normal? quickly grow as a specialist, reach a confident middle, and as a result I am engaged in stamping tasks of the same type that are not related to web development and .NET tools. The desire to develop and gain experience disappears, since there is not even a basis for this. From this question, when is a junior allowed to do normal tasks on such ready-made projects in such companies and is it allowed at all? Should I leave for another company where the scope and experience will be normal? quickly grow as a specialist, reach a confident middle, and as a result I am engaged in stamping tasks of the same type that are not related to web development and .NET tools. The desire to develop and gain experience disappears, since there is not even a basis for this. From this question, when is a junior allowed to do normal tasks on such ready-made projects in such companies and is it allowed at all? Should I leave for another company where the scope and experience will be normal?

Answer 1

when juna is allowed to do normal tasks

When the team leader thinks that June is ready for this.

and are they allowed at all?

Depends on the company.

Should I leave for another company where the scope and experience will be normal?

A year later, to have the opportunity to choose.

Answer 2

I got a job with a great desire to constantly learn and apply something new, quickly grow as a specialist, reach a confident middle, and as a result I am engaged in stamping tasks of the same type that are not related to web development and .NET tools.

Well, these are your personal problems. Work is not a school, not an institute, and not courses. At work, the customer pays for what the customer wants, not what the developer wants.

The desire to develop and gain experience disappears, since there is not even a basis for this. From this question, when is a junior allowed to do normal tasks on such ready-made projects in such companies and is it allowed at all?

This question is completely unnecessary on the Internet. Ask your team leader. Not all projects have "normal tasks" as you see them. Somewhere, after all, the product has already been written, people use it, and nothing needs to be finalized in it. Easy to maintain - solve maintenance problems, maybe fix bugs, maybe update something to make the product run on a newer version of java or hardware.
And this is NORMAL. From the user's point of view, would you be interested in buying a car, and then paying another 10% of its cost every month for the fact that every month the shape of the doors changes, or the diameter of the wheels, or something else? I think not, you would like to buy a car once and not climb under the hood for several years.

At the same time, my curator explained that most of the tasks are of this kind, but his experience and his tasks suggest that there are still many normal tasks, like using ASP.NET, API implementation, the structure of the web system itself, and other things. .

Experience may indicate that such tasks could have been in the past, but now they have already been solved. Also, experience could be gained on other projects.
At the same time, competent work with branches and git is also not bad. Within your current work, you can become a key specialist - this is when you know not individual technologies, frameworks and languages, but you know the project itself, what components there are, how they work together, who uses them and why, so that you can make a decision yourself, for example, about significant rework of any part of the component, and at the same time that the business is not affected. That is, you can study the product itself.
Well, in general - yes, there are projects where there is more development from scratch, there are projects where there are a lot of migrations and refactorings, where there is more than just support. And specialists are needed everywhere.

Answer 3

The customer pays For: completing the task
The customer does not pay for:
* leapfrog frameworks
* your learning surprise surprise
* for interesting tasks (although there is a negative payment in game dev)
* does not pay for "code quality" *
* does not pay for documentation *
* does not pay for tests *
* what is marked with asterisks is a must for long running projects

Answer 4

I got a job with a great desire to constantly learn and apply something new, quickly grow as a specialist, reach a confident middle, and as a result I am engaged in stamping tasks of the same type that are not related to web development and .NET tools.

You had to throw out all this sheet to the team leader, and if you are too good for such tasks, automate the processes so that these tasks of the same type either do not appear or are completed as soon as possible.

Answer 5

The same as the rest after the task is simpler