When working in agile environments / UCD environments I think you learn/understand to "let go". Sometimes a feature just does not test well with users, no matter how much business analysis/prototyping we do. I think also a large chunk of code that hasn't gone through that sort of rigour - even though it's great code - you shouldn't be too attached to. An engineer doesn't have that sort of skill set to determine if features are worth it.
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.
When working in agile environments / UCD environments I think you learn/understand to "let go". Sometimes a feature just does not test well with users, no matter how much business analysis/prototyping we do. I think also a large chunk of code that hasn't gone through that sort of rigour - even though it's great code - you shouldn't be too attached to. An engineer doesn't have that sort of skill set to determine if features are worth it.