Often, this is called being a "product minded" engineer. It always makes sense to understand the business domain and the problem the software is trying to solve. It might not require drastic changes such a this one, but it will inform even tiny decisions you have to make, like what wording to use or if you focus a certain field or not. Those tiny decisions can have a HUGE impact.
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.
Often, this is called being a "product minded" engineer. It always makes sense to understand the business domain and the problem the software is trying to solve. It might not require drastic changes such a this one, but it will inform even tiny decisions you have to make, like what wording to use or if you focus a certain field or not. Those tiny decisions can have a HUGE impact.