One of the most salient features of our Tech Hiring culture is that there is so much bullshit. Everyone knows this. Each of us contributes his share. But we tend to take the situation for granted.
Regarding your (good !) point on consistency, in my case I would put it under "refactoring", because I'm just unable to start with something consistent and coherent first.
So
I start with what Anne Lamott would call a shitty first draft
Later I notice the inconsistencies
Then I refactor it to sanity - JetBrains IDE do wonder here
Then I write unit tests ensuring that my naming conventions stay coherent forever
Not a bad point at all. I separated them because I feel we must think of consistency on it's own and refactoring encapsulated a lot more than just this. But I agree, first make it work, then make it good. But, if you can make it decent from early on, it will be easier to do so.
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.
Regarding your (good !) point on consistency, in my case I would put it under "refactoring", because I'm just unable to start with something consistent and coherent first.
So
Not a bad point at all. I separated them because I feel we must think of consistency on it's own and refactoring encapsulated a lot more than just this. But I agree, first make it work, then make it good. But, if you can make it decent from early on, it will be easier to do so.