How to stop cooking in your own code?

Question

Java

Guys, tell me how to stop cooking in your own code, the topic is relevant, especially for juniors, which I am! I work in a company, but as such, there is no mentoring from more experienced colleagues, it works well, okay, but as it is written, what is written is not of interest, I myself feel that it could be better, but I don’t know how to do it better, and this is how it turns out that I cook in my own code, especially since I’m also a junior, for a junior, in general, you need as many good and sensible examples as possible in order to gain experience, and in this regard, the question is, how to stop cooking in your own code? how to learn to write better, cleaner and more competently? where to get examples? In general, all your advice and instructions will be extremely useful.

Answer 1

If the result of your work is built into a chain where more experienced colleagues participate and you are not driven around the office for every bug found, then it is likely that they are satisfied with the quality of your work.
Well, no one will work as a nanny-mentor. It should be questions from your side.

Answer 2

Well, you have already been written about the angular styleguide . I will also add that it would be nice to read about SOLID principles in relation to javascript and, in principle, teach javascript itself. Also, finally figure out what MVC is (do not read one article, for almost 40 years these three letters have come to mean too many different things for many people), MVVM, etc. There is also a nice list of questions that can be used as a roadmap for learning angular. But even more profit will be given by the introduction of TDD.
Since no one is engaged in mentoring, then find yourself one. And preferably not alive, since living mentors are prone to subjectivism.
The ideal mentor is unit tests. Moreover, they will represent the main value for you when you have not yet written the code that you are going to test.
Let's say you were given a task - to write some small thing. Before you sit down and write, at the stage when you want to think about how you will do it, write a test. If you don't feel comfortable testing your code, or something strange comes up, that's a signal that something went wrong. Figure out what's stopping you. Perhaps something can be moved to a separate service or something else. Perhaps your code under test is taking on too much.
In a word ... if tests are easy to write and easy to maintain, then you are doing well. If not, then everything is bad and you need to clean up the code. However, since your code is covered with tests, you can do this without worrying too much about regressions.
well, try more, experiment. Again, this requires testing.
I have formulated some personal rules for myself that I follow, and this allows me to write testable code. Some of these rules I have already voiced here .

Answer 3

Github is big, there are many projects. Study. You can even participate in several.

Answer 4

As an option to change jobs.
Different projects, different teams - more experience.