I'm a developer who likes testing first, iterative processes, and refactoring, and I care about quality. I speak both C and Ruby with some facility, and enjoy both, which confuses some people.
I'm most disconcerted not by one person or the other arguing that point A is more important than point B (at least sometimes), but by the fact they think it has to be a choice. Being inclusive and insisting on quality at all times can be perfectly compatible, if done well. It's only when you don't care enough about the consequences of your inclusiveness, or about the quality of your quality (yes, really), that reductive, facile thinking backs us into a corner where someone's baby has to be thrown out with the bathwater (to mix a metaphor).
False dilemmas don't solve problems. They just ignore half the problem.
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.
I'm most disconcerted not by one person or the other arguing that point A is more important than point B (at least sometimes), but by the fact they think it has to be a choice. Being inclusive and insisting on quality at all times can be perfectly compatible, if done well. It's only when you don't care enough about the consequences of your inclusiveness, or about the quality of your quality (yes, really), that reductive, facile thinking backs us into a corner where someone's baby has to be thrown out with the bathwater (to mix a metaphor).
False dilemmas don't solve problems. They just ignore half the problem.