The first step is done, which is, identify there's an issue.
As a junior developer the attitude is all that will define your future. I liked the way you asked for help, you got my attention.
I'll try to give you some advice. There are a lot of things you can do, however, you should try to choose them wisely, hard thing.
Communication is the main key, if they have issues with you, you have to raise questions to them immediately. You must show interest, must show you are trying to solve solutions but as a team you must do it together.
As software developer, you'll have to learn tools to analyse how your performance's website is. Such as lighthouse Google tool.
As a project developer, you'll have to learn how the users use your product. There are tools that track the required information such as Google Analytics.
I'd say that mainly try to follow simple ideas, that you can iterate later on, focus on performance, release reliable code and share what you are doing and what you expect from what you'll try to do.
That is not eas, finding the balance is an art, the time usually comes against
Thanks Carlos for giving me the insight to see the project from three perspective. I used the tools a bit but not so much. I will surely look onto those.
You must show interest, must show you are trying to solve solutions but as a team you must do it together. - That's a great advice. I try to solve problems sometimes and come with some solutions but doesn't share it with the team that much. How do you think to do that with the team?
Like, I can say a scenario. The application had no global error handling mechanism. I searched some solutions and implemented an interceptor to handle and show the notifications recently. But, no one never knows that. And as most of them are back end developers, they can give less feedback about these issues. So, how do I share these with team or client(for freelance projects)?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The first step is done, which is, identify there's an issue.
As a junior developer the attitude is all that will define your future. I liked the way you asked for help, you got my attention.
I'll try to give you some advice. There are a lot of things you can do, however, you should try to choose them wisely, hard thing.
I'd say that mainly try to follow simple ideas, that you can iterate later on, focus on performance, release reliable code and share what you are doing and what you expect from what you'll try to do.
That is not eas, finding the balance is an art, the time usually comes against
Hope it helps
Thanks Carlos for giving me the insight to see the project from three perspective. I used the tools a bit but not so much. I will surely look onto those.
You must show interest, must show you are trying to solve solutions but as a team you must do it together. - That's a great advice. I try to solve problems sometimes and come with some solutions but doesn't share it with the team that much. How do you think to do that with the team?
Like, I can say a scenario. The application had no global error handling mechanism. I searched some solutions and implemented an interceptor to handle and show the notifications recently. But, no one never knows that. And as most of them are back end developers, they can give less feedback about these issues. So, how do I share these with team or client(for freelance projects)?