What do you do if you receive vague and unhelpful feedback on your algorithms?

1 Seek Clarification

When faced with unclear feedback, your first step should be to seek clarification. Reach out to the person who provided the feedback and ask for specific examples or details that led to their comments. It's important to approach this conversation with an open mind and a genuine desire to understand their perspective. Remember, the goal is to improve your algorithm, not to defend it. By asking questions like, "Could you elaborate on what you mean by 'inefficient'?" or "What specific part of the algorithm did you find confusing?", you can gather actionable insights.

2 Reflect Objectively

After obtaining more detailed feedback, take a step back and reflect on it objectively. This means setting aside any personal attachment to the algorithm and considering the feedback from a purely technical standpoint. Consider if the feedback points to an issue with algorithm complexity, efficiency, or perhaps a lack of comments in your code that makes it hard to understand. This self-reflection can be challenging but it's crucial for growth. You might find that the feedback, once vague, actually highlights valid areas for improvement.

3 Improve Documentation

Good documentation can often clarify misunderstandings about an algorithm's design and purpose. If feedback suggests that your algorithm is hard to follow, consider improving the comments within your code or creating a more detailed documentation file. This should clearly explain the algorithm's functionality, its inputs and outputs, and any assumptions it makes. Clear documentation not only aids in understanding but also serves as a guide for future revisions or when other developers need to work with your code.

4 Revise and Test

With a clearer understanding of the feedback, begin revising your algorithm. Focus on the areas identified as problematic and make the necessary changes. After revising, it's crucial to thoroughly test the algorithm to ensure that your changes have had the desired effect and haven't introduced new issues. Testing might involve unit tests, which are automated tests that check individual parts of the algorithm, or more comprehensive integration tests that assess how well the algorithm works within the larger system.

5 Share Updates

Once you've made revisions, share the updated algorithm with those who provided the original feedback. This not only demonstrates your responsiveness but also invites further constructive criticism that can lead to even better improvements. Sharing updates can also foster better communication and understanding among your colleagues or peers. It shows that you value their input and are committed to excellence in your work.

6 Maintain Perspective

Finally, it's important to maintain perspective throughout this process. Receiving feedback, even when vague or seemingly unhelpful, is a normal part of professional development. Use it as a learning opportunity and remember that every algorithm can be improved. Staying positive and proactive about incorporating feedback will help you grow as a developer and enhance the quality of your work over time.

7 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?