Staying curious about others' perspectives is the first step in growing from feedback. 1. Clarify - Reach out and ask specific questions to really understand what the feedback is about and why it matters. 2. Make Changes - Take a look at your code and make the suggested tweaks to improve things whether that’s simplifying logic or following best practices. 3. Collaborate - Sit down with the person who gave you feedback to brainstorm better solutions together. 4. Test - After making your changes, test everything thoroughly, and don’t hesitate to ask for more feedback to see if the changes hit the mark.

During my internship, I often received feedbacks from my manager, both constructive and critical. Here are my approaches: - I took the time to reflect and understand the areas where I could improve. - I wouldn’t hesitate to ask for clarification. - I would try different approaches in my coding to see which one worked best . - I identified my weaker areas and actively worked on them by learning new techniques. - I often sought advice from my colleagues to get their perspectives on my improvements. - I always ran thorough unit tests and other checks to ensure my code was bug-free - I viewed feedback as an opportunity for growth and consistently worked to improve my skills. - I always kept an open mind when receiving feedback. Hope this helps

I would start by listening carefully to the feedback and asking clarifying questions to ensure I fully understand it. I would then reflect on my current practices to identify areas for improvement and research best practices or new techniques relevant to the feedback. Experimenting with different approaches in test cases would help me see what works best. Collaborating with peers or mentors for additional insights would provide valuable perspectives. After implementing changes, I would document what I've learned and seek further feedback to continually refine my approach. Throughout this process, I would maintain a positive attitude to foster growth and improvement.

When feedback challenges your coding approach, embrace it as a chance to level up. Here's how to make it work for you: Digest the feedback: Take a step back and truly understand what’s being suggested. Explore alternatives: Dive into research to uncover new methods and best practices. Apply and iterate: Try out the suggestions in your code and assess the impact. Instead of seeing critiques as setbacks, treat them as stepping stones to refine your skills.

Just accept it. Then after a critical analysis (don't let your ego mess this part), you should be able to get the most of the feedback without blinding yourself with some king of anger or negative emotions.