Great lesson dude. As I learn from my experience, we do not have to decide it all by our self. After doing sufficient analysis, we should communicate with our team what should we decide based on our analysis. It would be better if we come with our proposed solution. Thanks I learn much from your article.
Good point! It's something I didn't do so much early on, but as I grew more comfortable in the team I would discuss approaches more and more with them to seek validation or get insights from other perspectives (when I was stuck). Recognising when you're not making valuable progress and being able to reach out towards your teammates are important things to keep in mind!
Thanks for the feedback! 🙏
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.
Great lesson dude. As I learn from my experience, we do not have to decide it all by our self. After doing sufficient analysis, we should communicate with our team what should we decide based on our analysis. It would be better if we come with our proposed solution. Thanks I learn much from your article.
I think this is what most people do. I did this few times myself
Good point! It's something I didn't do so much early on, but as I grew more comfortable in the team I would discuss approaches more and more with them to seek validation or get insights from other perspectives (when I was stuck). Recognising when you're not making valuable progress and being able to reach out towards your teammates are important things to keep in mind!
Thanks for the feedback! 🙏