The quality of outcome (how reliable, performant and stable to edge cases your feature is).
Clean code will eventually and naturally come. Don't waste your energy starting from wrong side.
That may be the bigger problem - listening to feedback is a great way to improve. If receiving that feedback makes you feel bad about your work, fix that response. Embrace the feedback as mentoring towards being a better developer, and be thankful for it. Easier said than done, but if you can adopt a positive attitude towards receiving feedback, odds are you'll be more comfortable taking the advice from your manager and get to a place where you both are happy with your work.