Since it seems evident it needs to be explained. Do not expect me to take 100% of your criticism like you are a prophet. I will evidently evaluate/criticise your own criticism, relating it to the purpose of the thing getting criticised on.
If it doesn't match with what I'm going for, I will not use the criticism stated. This also includes if the criticism in question, is also explained and elaborated.
For example, many tell me to use "local" variables, but never truly elaborate to why, except stating readability or that it'd continue on throughout the entire scope (which, in the situation it is mostly stated in, is what I want it to do).
And I don't "take no criticism", I take criticism, evaluate it and figure out ways to apply it, if I can't, I say I can't. This is not being "stubborn", this is figuring out how the criticism applies to the situation and not being spoon-fed criticism.
I will be honest, the only thing I spoon-feed is math-stuff, since that is my weakest point when it comes to coding. However, I plan to get to learning more math later on.